The World of Computer Software/The World of Computer Software.iso/uupc11xd.zip/HINTS.SPB

Text File | 1992-12-18 | 114KB | 2,372 lines

From barnacle.erc.clarkson.edu!sun.soe.clarkson.edu!uupc-info-request Thu, 03 Sep 1992 14:16:48 EDT remote from mit-eddie
Received:  from mit-eddie by kendra.kew.com (UUPC/extended 1.11v) with UUCP;
           Thu, 03 Sep 1992 14:16:48 EDT
Received: from barnacle.erc.clarkson.edu by eddie.mit.edu id aa29748;
          3 Sep 92 14:02 EDT
Received: from sun.soe.clarkson.edu by barnacle.erc.clarkson.edu with SMTP (PP)
          id <[e-mail]>;
          Thu, 3 Sep 1992 13:47:40 -0500
Received: by sun.soe.clarkson.edu (4.1/SMI-4.1) id AA12220;
          Thu, 3 Sep 92 13:25:27 EDT
Return-Path: <gstream!gstream.com![e-mail]>
Received: from nwnexus.wa.com by sun.soe.clarkson.edu (4.1/SMI-4.1) id AA12172;
          Thu, 3 Sep 92 13:24:48 EDT
Received: by nwnexus.wa.com id AA08084 (5.65c/IDA-1.4.4
          for [e-mail]); Thu, 3 Sep 1992 10:25:44 -0700
Received: by gstream.com (UUPC/extended 1.11r); Thu, 03 Sep 1992 09:49:57 PDT
Date: Thu, 03 Sep 1992 09:49:47 PDT
From: "Blake C. Ramsdell" <[e-mail]>
Message-Id: <[e-mail]>
Organization: GlobalStream Corporation (West Coast)
To: "William R. Ward" <[e-mail]>
Cc: UUPC Mailing List <[e-mail]>
Subject: Re: Query: -ssite,any

On Wed, 02 Sep 1992 13:49:12 PDT, "William R. Ward" <[e-mail]>
wrote:
> Is there some way to tell UUPOLL to call a particular site at the
> specified interval, and also to call any site for which outgoing mail
> is queued, but only if there is outgoing mail queued?
>
> I poll three sites which can poll me, and one which can't.  I would
> like to make it so that the one which can't poll me gets polled every
> hour, and at that time if there is mail queued for any of the other
> three, they get polled too.
>
> If this is not currently possible (I don't think it is), I suggest
> the syntax "-ssite1,site2,Any" as a legal way to specify more than
> the simple "-ssite1" or "-sall" or "-sany".

I use UUPC 1.11r currently, and this information is extracted from the docs
for 1.11q (the last docs version) from COMMANDS.TXT under UUPOLL:

            -s system System name to poll.  Default is "all" followed by
                      "any", which cannot be explicit specified.
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                             !
                             (I'm not sure what this means...)

We have a network installation here, and a dedicated machine that runs
UUPOLL all day.  We invoke UUPOLL from a batch file (CALLANY.BAT) that
forces a poll to them every twelve hours.  The following is CALLANY.BAT:

uupoll -i 0005 -d 1200 -s any
uustat -P nwnexus
callany

This basically checks to see if there's any work to be done every five
minutes (-i 0005), and terminates after 12 hours (-d 1200).  After UUPOLL
terminates, the batch file takes over and forces a poll to our mail server
(nwnexus) and then runs itself again.  After UUPOLL runs for five minutes
this second time, it notices that it has work to do (the poll I did) and
calls NWNEXUS.

If you want to poll the site that can't poll you every hour, just change
the -d 1200 to -d 0100 and change the NWNEXUS to the name of the site
you want to poll every hour.

If there is mail to go out, it will automatically get sent at most after
the interval specified by "-i".

Is this what you wanted to know, or am I completely out of the park?

Blake
--
Blake C. Ramsdell              |   Voice:    [phone]
GlobalStream Corporation       |   FAX:      [phone]
5122 Olympic Dr. NW Ste. A102  |   UUCP:     nwnexus!gstream!blake
Gig Harbor, WA  98335          |   Internet: [e-mail]





















From mit-eddie!sun.soe.clarkson.edu!uupc-info-request Sat, 15 Jun 1991 18:10:11 EDT remote from kendra
Received:  from mit-eddie by kendra.kew.com (UUPC/extended 1.11(experimental));
           Sat, 15 Jun 1991 18:10:11 EDT
Received: from OMNIGATE.CLARKSON.EDU by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA29867; Sat, 15 Jun 91 17:44:57 -0400
Received: from sun.soe.clarkson.edu by omnigate.clarkson.edu id aa25330;
          15 Jun 91 17:26 EDT
Received: by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA27530; Sat, 15 Jun 91 16:31:31 EDT
Return-Path: <omega![e-mail]>
Received: from mcsun.EU.net by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA27526; Sat, 15 Jun 91 16:31:18 EDT
Received: from kestrel.ukc.ac.uk by mcsun.EU.net with SMTP;
    id AA04474 (5.65a/CWI-2.94); Sat, 15 Jun 91 22:31:10 +0200
Received: from cctal by kestrel.Ukc.AC.UK   with UUCP  id aa17921;
          15 Jun 91 21:21 BST
Received: by cctal.uucp (smail 2.3)
    id AA14000; 15 Jun 91 12:12:01 PDT (Sat)
Received:  by omega.uucp (UUPC/extended 1.09d);
           Sat, 15 Jun 1991 19:07:20 gmt
Date:      Sat, 15 Jun 1991 19:07:18 gmt
From: Andrew Hardie <mit-eddie!relay.eu.net!omega!ash>
Message-Id: <[e-mail]>
To: "UUPC-info list uupc-info"@sun.soe.clarkson.edu
Subject:   Unix Permissions file

There was some traffic on the net recently about problems with using UUPC
to talk to unix system that have the /usr/lib/uucp/Permissions file.

Having had these problems and sorted them out by a combination of repeated
RTFM'ing, calling Tech Support at a SCO supplier and guesswork, I have
worked up a reasonable rule of thumb which, although probably excessively
lax for the very security conscious, works ok for me.

The Permissions file has entries for LOGNAME (for incoming calls from other
machines) and MACHINE for outgoing calls to other machines. Fine. The one
point more often missed than any other seems to be the caveat that for
those systems that call you, ALL THEIR LOGIN IDS MUST APPEAR IN A SINGLE
LOGNAME ENTRY. This one can drive you potty. You put in one system and it
works. You add a second, as a second LOGNAME entry and it doesn't work.
You are looking at everything else except Permissions because you *know*
uucp must be OK because the first system is working!

My Permissions file looks like this (names changed to protect the guilty):

LOGNAME=usys1:usys2:usys3:usys4:usys5:usys6:usys7:usys8:usys9:usys10 \
        COMMANDS=rmail:rnews:uucp \
        READ=/ \
        WRITE=/ \
        SENDFILES=yes REQUEST=no

MACHINE=sys1:sys2:sys3:sys4:sys5:sys6:sys7:sys8:sys9:sys10 \
        COMMANDS=rmail:rnews:uucp \
        READ=/usr/spool/uucppublic:/usr/tmp:/tmp \
        WRITE=/usr/spool/uucppublic:/usr/tmp:/tmp \
        SENDFILES=yes REQUEST=no

I have always made a habit of giving each incoming system a separate login id
formed from the name of the system with "u" added. I find it makes tracking
easier. Hence, LOGNAME shows "u"sys1 and MACHINE shows just sys1.

If you are just running plain vanilla HDB UUCP, then just make sure the
/usr/lib/uucp/Systems file is right and the mail should flow. If you are
running mmdf (e.g. SCO UNIX), then for the outgoing mail to get anywhere
you need to make sure that the uucp files in /usr/mmdf/table are OK, (unless
you are routing out through a single or smart host by just using the badhosts
channel to forward everything unrecognised to somewhere else) e.g.:

#
#   uucp.chn
#

sys1.UUCP:     sys1!%s
sys2.UUCP:     sys2!%s
... etc ...

#
# uucp.dom   domain file for all *.UUCP
#

sys1:  sys1.UUCP
sys2:  sys2.UUCP
... etc ...

Hope this helps anyone who has been struggling with this!
I'm sure someone will write in to point out that I have got this all wrong!

Andrew
--

+----------------------------------------------------------------------------+
|  Andrew Hardie                                             [e-mail]  |
|  London, England                                      ukc!cctal!omega!ash  |
+----------------------------------------------------------------------------+





















From mit-eddie!sun.soe.clarkson.edu!uupc-info-request Sun, 18 Aug 1991 15:27:13 EDT remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11h) with UUCP;
           Sun, 18 Aug 1991 15:27:13 EDT
Received:  from mit-eddie by kewgate.kew.com (UUPC/extended 1.11g) via UUCP;
           Sun, 18 Aug 1991 14:19:48 EDT
Received: from OMNIGATE.CLARKSON.EDU by eddie with SMTP (5.65/25-eef)
    id AA07731; Sun, 18 Aug 91 13:04:04 -0400
Received: from sun.soe.clarkson.edu by omnigate.clarkson.edu id aa21582;
          18 Aug 91 12:01 EDT
Received: by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA20234; Sun, 18 Aug 91 11:56:15 EDT
Return-Path: <omega![e-mail]>
Received: from mcsun.EU.net by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA20220; Sun, 18 Aug 91 11:56:07 EDT
Received: from kestrel.ukc.ac.uk by mcsun.EU.net with SMTP;
    id AA04589 (5.65a/CWI-2.101); Sun, 18 Aug 1991 17:55:34 +0200
Received: from cctal by kestrel.Ukc.AC.UK   with UUCP  id aa17320;
          18 Aug 91 16:54 BST
Received: by cctal.uucp (smail 2.3)
    id AA13488; 18 Aug 91 16:42:10 BST (Sun)
Received:  by omega.UUCP (UUPC/extended 1.11f);
           Sun, 18 Aug 1991 15:34:54 GMT
Date:      Sun, 18 Aug 1991 15:34:28 GMT
From: Andrew Hardie <mit-eddie!relay.eu.net!omega!ash>
Message-Id: <[e-mail]>
To: UUPC Mailing List <[e-mail]>
Subject:   PC-ELM and UUPC

There has been some netchat recently about using PC-ELM with UUPC.
Herewith my experiences ...
I obtained the PC-ELM 2.1 archive. The archive is incomplete. In particular,
it did not contain the file PCENV.BAT, referred to in what passes for the
documentation, which shows example of how to configure the environment
variables. I found that the only variable which has to be set is HOME, to
point to the directory containing the PC-ELM config file, which *is*
called ELM.RC (docs say it is called BM.RC but can be changed in the
source to be somthing else - someone has already done this!). I set the
ELM.RC file as follows:

# configuration file for Bdale's Mailer... format is:
#        host <space> this_host_name
#        uucphost <space> UUCP host name
#        user <space> this_user_name
#        fullname <space> your full name for mail headers (optional)
#        reply <space> your reply address if not this machine (optional)
#                  useful for pc on large network off smart hosts
#        smtp <space> path to mailboxes          default /spool/mail
#        edit <space> path your editor (optional)
#        maxlet <space> max number of message in mbox ( optional default 300)
#        video <1|0> direct | bios video mode ( turbo C only default direct )
#        startmode <0|1> uucp v nos mail standards - use 1 mostly
#        zone <space> your timezone
#
host omega.uucp
uucphost omega
user ash
fullname Andrew Hardie
reply [e-mail]
edit c:\usr\bin\ed.exe
smtp /tmp/ash
maxlet 600
video 1
startmode 0
zone GMT

Originally, I had the startup mode set to 1 (nos/smtp mailbox). This read
a mailbox file OK, provided it was called (in my case) ash.txt. For the
startmode of 0 (uucp), nothing - complained that it "could not stat file
c:/tmp/ash/ash." Made a file called c:/tmp/ash/ash. - still no luck.
Looked at the code - in uucp mode, it looks for separator lines the begin
"From uucp"; that went out in UUPC ages ago (right Drew?). I am no C
programmer and although I do have Turbo C I couldn't be bothered to set it
up to fix this. However, I am a great fan of patching binaries with NU.
Attacked PCELM.EXE; changed the first instance of "From uucp" to "From <00>"
(where <00> is binary 00, which I assume to be a string terminator in Turbo
C parlance. It now read the mailbox, but was fooled by lines in a mail file
that started "From ", even though they weren't the real start. Tried changing
the string to "CR LF From <00>"; no good. Then I tried changing the entire
"From uucp" string to all binary 01s, as used by UUPC as the mail message
separator. This worked a treat; read the file reliably and was no longer
fooled by the false From lines. There is a second instance of "From uucp"
in the file; I didn't change that as I didn't know what it did - may be for
outgoing?

Next, I tried a reply and got the "From /dev/null!ash" problem, as described
by a number of correspondents. Looked at the code to see where it invokes
rmail. Remembered that someone had said that rmail may need to be invoked
with the -t option in this circumstance. Tried patching the part of the
binary that had "rmail %s < UUCPMAIL.$$$" to "rl -t %s < UUCPMAIL.$$$", with
rmail.com copied to rl.com, so as to keep the string the same length.
rmail complained about "missing or additional" stuff on command line. Then
tried "rmail -t < UUCPMAIL.$$$", assuming that rmail was supposed to find
the intended recipient from the "To: " line in the message (in the absence
of any docs for rmail ...). rmail then complained that there was no-one to
send the message to. Got bored with this and then just changed the "rmail
%s < UUCPMAIL.$$$" to "mail  %s < UUCPMAIL.$$$" (note the two spaces before
%s, again to keep thestring the same length). This worked, both on replies
and for originating mail within PC-ELM and had the additional benefit of
appending my UUPC .sig file which PC-ELM does not support (I don't think!).

Drew: I'd appreciate knowing whether this is "A Bad Thing" to do and
where "rmail" is appropriate (I thought it was only for delivering mail,
not creating or replying). Perhaps PC-ELM can't make up its mind whether
it is a User agent or a Mail agent!

After I had finished messing about with this, I found 4 lost clusters,
as reported by another correspondent. I have not used PC-ELM sufficiently
after having fixed the /dev/null and invisible mailbox problems to say
whether this problem has gone away, but I suspect not. One problem does
remain, for sure: when replying to a message in PC-ELM, with include, an
arbitrary binary character gets (usually with bit 8 set) gets included at
the start of the included section. I have a feeling this code is doing
some absolute referencing during random disk access (you can tell I know
what I'm talking about here, can't you :-)) and that this may explain this
and the lost clusters (which all contained PC-ELM headers, followed by
whatever happenned to be on the disk at that point). As they say here in
England, I think the code needs going through with a Bren gun.

That said, PC-ELM *does* provide a front end for UUCP better suited to the
novice or casual user and, if it wasn't for the reply and lost cluster
problems, I would put it in front of the ten or so UUPC users I support.
One thing I definitely do not like, but the new users wouldn't notice,
is that the meaning of the X and Q commands are swapped, i.e., in PC-ELM,
Q leaves the mailbox unaltered and X saves changes and exits.

If there is enough interest in PC-ELM amongst the UUCP users and they
are having difficulty getting it and there are some C programmers out there
who fancy exercising their skills in making this into a rock-solid frontend
for UUPC, I am happy to send it to Drew or someone he cares to nominate,
so that it can be put up on sun.soe.clarkson.edu. No individual e-mail
requests, please; after all, I am in England! The ZIP is 116683 bytes.

Reading the notes at the start of the main source code file (TCMAIN.C),
it became clear that PC-ELM is *not* a port of the highly recommended (but
not yet made to compile by me!) unix program of the same name. It started
life as an extension of the mailer supplied with KA9Q, that most mysterious
and legendary of programs, which does everything except make tea, if its
proponents are to be believed! Primarily, it was intended for the Amateur
Packet Radio environment (NET/ROM, AX.25, and all that) but then included
SMTP and TCP/IP and thus started to stray into DOS/unix territory and get
used as a router, including doing routing between TCP/IP and Novell IPX
environments (ask me how if you are interested!). It had a simple mailer,
called BM (for Bdale's Mailer, after Bdale Garbee, who wrote it). This
then got taken over by a number of other radio types, mostly European,
it seems, including Trulli, Freiss, Siebeck and, finally, Kelvin Hill,
whose call sign is G1EMM, which explains those g1emm directories you see
on KA9Q ftp sites! At some point in its evolution, the idea of using a
user interface like the unix ELM was adopted.

The fact that it handles both UUCP mail (which I have now got working)
and SMTP mail (which I have not yet tried) in the one program and that
you can cross-reply between these is a plus. The lack of any kind of
mmdf channel handling or sendmail rule processing will, I think, make
its use in such a dual-universe environment only suitable for "end-user"
nodes ("leaf" in uucp parlance). It is clear that the people working on
PC-ELM have not looked at UUPC in a *long* time. The last revision date
on the V2.1 of PC-ELM is October 1990; if anyone knows of a later version,
do tell. Tantalisingly, one of the revision notes mentions the addition
of NNTP traffic handling - nothing mentioned in the docs and, not having
a newsfeed here and, consequently, not knowing anything about NNTP, I can't
tell by casting my ignorant eye over the code what support it provides.

I'll end by saying that the difference in programming quality between PC-ELM
and Drew's work with UUPC *really* shows! Now, if Drew could be persuaded
to take a look at PC-ELM .... The front end is OK, it's how it interfaces
to the back end (and the disk!) that is the problem. Someone who knows a
good bit about KA9Q is probably a must; do we have any KA9Q experts amongst
the UUCP worldwide fraternity?

Hope this provides a useful review of PC-ELM.

Andrew
--
+----------------------------------------------------------------------------+
| Andrew Hardie                                               [e-mail] |
| London, England                                        ukc!cctal!omega!ash |
+----------------------------------------------------------------------------+





















From mit-eddie!sun.soe.clarkson.edu!uupc-info-request Wed, 20 Nov 1991 21:57:48 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11o) with UUCP;
           Wed, 20 Nov 1991 21:57:48 EST
Received:  from mit-eddie by kewgate.kew.com (UUPC/extended 1.11o) with UUCP;
           Wed, 20 Nov 1991 00:13:05 EST
Received: from OMNIGATE.CLARKSON.EDU by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA02946; Wed, 20 Nov 91 00:02:58 -0500
Received: from sun.soe.clarkson.edu by omnigate.clarkson.edu id aa00418;
          19 Nov 91 20:53 EST
Received: by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA27353; Tue, 19 Nov 91 20:44:05 EST
Return-Path: <wang!altacoma.wang.com![e-mail]>
Received: from relay2.UU.NET ([137.39.1.7]) by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA27330; Tue, 19 Nov 91 20:44:00 EST
Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay2.UU.NET with SMTP
    (5.61/UUNET-internet-primary) id AA24755; Tue, 19 Nov 91 20:42:54 -0500
Received: from elf.UUCP by uunet.uu.net with UUCP/RMAIL
    (queueing-rmail) id 204118.29593; Tue, 19 Nov 1991 20:41:18 EST
Received: from altacoma.wang.com by elf.wang.com
    id aa14639; Wed, 20 Nov 91 1:06:36 GMT
Received:  by AltaComa.wang.com (UUPC/extended 1.11n);
           Tue, 19 Nov 1991 19:59:04 EST
Date:      Tue, 19 Nov 1991 19:59:03 EST
From: "William W. Plummer" <mit-eddie!altacoma.wang.com!plummer>
Message-Id: <[e-mail]>
To: UUPC-Info <[e-mail]>
Subject:   MAKE-O-MANIA

For those who like to roll their own,  I just did a bit of experimenting
with various make programs.  I built only the DOS version of UUPC.  Of
course we know that old MS make that came with MSC 5 will not work with
the current nmake  file, but the make that comes with MSC 6, 6.00A and
6.00AX will.  The new  nmk  program also works very well by saying,
   nmk /nologo /s /f nmake installR     .   Polymake, however, chokes
on much of nmake (Ask me if I really care!).  FYI.  --Bill
--
William W. Plummer        H:  508-256-9570
7 Country Club Dr.        [e-mail]
Chelmsford, MA  01824





















From mit-eddie!sun.soe.clarkson.edu!uupc-info-request Sun, 17 Nov 1991 12:20:47 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11o) with UUCP;
           Sun, 17 Nov 1991 12:20:47 EST
Received:  from mit-eddie by kewgate.kew.com (UUPC/extended 1.11o) with UUCP;
           Sun, 17 Nov 1991 08:11:12 EST
Received: from OMNIGATE.CLARKSON.EDU by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA07161; Sun, 17 Nov 91 07:25:01 -0500
Received: from sun.soe.clarkson.edu by omnigate.clarkson.edu id aa16871;
          17 Nov 91 5:53 EST
Received: by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA04222; Sun, 17 Nov 91 05:41:28 EST
Return-Path: <posmac![e-mail]>
Received: from sserve.cc.adfa.oz.au ([131.236.1.17]) by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA04218; Sun, 17 Nov 91 05:41:20 EST
Received: from posmac.UUCP by sserve.cc.adfa.oz.au (5.65c/1.34)
    id AA17581; Sun, 17 Nov 1991 21:39:43 +1100
Received:  by posmac.UUCP (UUPC/extended 1.11k);
           Sun, 17 Nov 1991 20:22:49 EST
Date:      Sun, 17 Nov 1991 20:22:44 EST
From: Mark Purcell <mit-eddie!sserve.cc.adfa.oz.au!posmac!msp>
Message-Id: <[e-mail]>
Reply-To: Mark Purcell <mit-eddie!sserve.cc.adfa.oz.au!posmac!msp>
To: [e-mail]
Cc: UUPC Mailing List <[e-mail]>
Subject:   Re: Can UUPC coexist with Netware


On Thu, 14 Nov 91 09:37:09 PST, "Tom Poage" <[e-mail]> wrote:
>
> So, has anyone tried to use UUPC on a NetWare host/server?
>
> If so, how does it handle multiple users/hosts?
>
> Is this even possible?

Well I currently have UUPC running over a Netware 3.11 network.
I only have one host so it makes things quite simple.  In fact using it this
way for local mail uucico is not even needed.  The mail command looks
after deliver and movemt of all mail.

I set up UUPC as if I had one machine with a number of users on it, as
per the docs.  Then in my netware system login script I assigned
the uupcuserrc variable to be dependant on the %LOGIN_NAME of the
user.  Something like:

SET uupcusrrc = "f:\lib\uupc\%LOGIN_NAME.rc"

Then it is a matter of creating a personal.rc file for each user who
is going to utilize mail.

After a bit of playing around it is all done.

Security is non existant as every user must have access to the ..\mail
directory they are required to write sent mail there.  But as most my
users are well behaved, security is not really a problem.

There is no such thing as a UUPC module, that I know of, that can be run
on the Netware host.  If you do wan't to run external mail delivery, ie
uucico, then you will have to envoke uucico from one of your hosts, any one.
But this can be done in the background under Windows in 386 eh mode.

As for delivery to multiple hosts, maybe if you map different users to
different drives it would be possible, but sound like too much trouble to
me,  better to keep all your mail in one spot.

If you do find any other solutions, or have any questions, feel free to
give me a yell.

Mark
--
Mark Purcell        UUCP:        uunet!sserve.cc.adfa.oz.au!posmac!msp
KINGSTON ACT        INTERNET:    [e-mail]
AUSTRALIA        PHONE: [phone]    INT:  [phone]
--
Mark Purcell        UUCP:        uunet!sserve.cc.adfa.oz.au!posmac!msp
KINGSTON ACT        INTERNET:    [e-mail]
AUSTRALIA        PHONE: [phone]    INT:  [phone]





















From mit-eddie!sun.soe.clarkson.edu!uupc-info-request Sun, 26 Jan 1992 07:26:50 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Sun, 26 Jan 1992 07:26:50 EST
Received:  from mit-eddie by kewgate.kew.com (UUPC/extended 1.11r) with UUCP;
           Sun, 26 Jan 1992 04:10:47 EST
Received: from OMNIGATE.CLARKSON.EDU by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA28668; Sun, 26 Jan 92 02:31:00 -0500
Received: from sun.soe.clarkson.edu by omnigate.clarkson.edu id aa15772;
          25 Jan 92 15:39 EST
Received: by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA01985; Sat, 25 Jan 92 15:00:10 EST
Return-Path: <@EDDIE.MIT.EDU:ffactory!ffactory.kew.com![e-mail]>
Received: from EDDIE.MIT.EDU by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA01981; Sat, 25 Jan 92 15:00:02 EST
Received:  by EDDIE.MIT.EDU with UUCP (5.65/25-eef)
    id AA14410; Sat, 25 Jan 92 14:58:22 -0500
Received:  from ffactory by kewgate.kew.com (UUPC/extended 1.11r) with UUCP;
           Sat, 25 Jan 1992 14:53:32 EST
Received:  by ffactory.kew.com (UUPC/extended 1.11r);
           Sat, 25 Jan 1992 14:47:05 EST
Date:      Sat, 25 Jan 1992 14:47:02 EST
From: Drew Derbyshire <mit-eddie!kew.com!ahd>
Message-Id: <[e-mail]>
Organization: Kendra Electronic Wonderworks
To: "Katherine E. Williams" <[e-mail]>
Cc: UUPC Mailing List <[e-mail]>
Subject:   Re: uupc

On Thu, 23 Jan 1992 00:27:24 PST, "Katherine E. Williams" <[e-mail]> wrote:
> you told me once but I forgot...
>
> How do I tell uupoll to call every n (5,10, whatever) minutes until
> it gets through, and then stop?

UUSTAT -P kendra                (creates dummy job to make -s any work)
UUPOLL -i hhmm -s any

Where hhmm = n in hours and minutes.  Once queue is empty, "-s any" will
not call any more.

-ahd-
--
Drew Derbyshire

Internet:       [e-mail]               U.S. Mail: Post Office Box 132
Voice:          617-641-3739                         Arlington, MA 02174

 Be careful, the last person using this keyboard had a terminal disease.





















From mit-eddie!kram.demon.co.uk!mt Sun, 26 Jan 1992 08:28:53 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Sun, 26 Jan 1992 08:28:53 EST
Received:  from mit-eddie by kewgate.kew.com (UUPC/extended 1.11r) with UUCP;
           Sun, 26 Jan 1992 08:19:18 EST
Received: from eros.uknet.ac.uk by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA02566; Sun, 26 Jan 92 06:22:19 -0500
Received: from demon.co.uk by eros.uknet.ac.uk with UUCP
          id <[e-mail]>; Sun, 26 Jan 1992 11:22:58 +0000
Received: from kram by office.demon.co.uk id aa05899;
          Sun, 26 Jan 92 11:22:05 GMT
Received: from bedroom by demon.co.uk (UUPC/extended 1.11r) with UUCP;
          Sun, 26 Jan 1992 10:21:08 gmt
Received: by kram.demon.co.uk (UUPC/extended 1.11r);
          Sun, 26 Jan 1992 10:04:05 gmt
Date: Sun, 26 Jan 1992 10:04:01 gmt
From: Mark Turner <mit-eddie!kram.demon.co.uk!mt>
Message-Id: <[e-mail]>
Organization: Demon Systems Limited
Reply-To: Mark Turner <mit-eddie!demon.co.uk!mt>
To: [e-mail]
Subject: Obtaining UUPC/Extended in the UK


Drew,

just for the record.... if anyone in the UK is having problems
obtaining new releases of UUPC/Extended (cos we don't have a real
Internet yet, but watch this space) we usually pull it down to
Demon within a few days and then upload it to Cix (The Compulink
Information eXchange). If any UK UUPCers would find it easier to
get the files from within the UK perhaps they could either use Cix
or suggest some suitable BBS over here that could hold the files.

Regards,

Mark.
--
 _ _     ___                            [e-mail]
| | |ark  |urner              ....uunet!uknet!demon!mt
Demon Systems, 42 Hendon Lane, Finchley, London N3 1TT
Work 081 349-0063, Mobile [phone]
Brown sauce makes it taste better!





















From mit-eddie!sun.soe.clarkson.edu!uupc-info-request Sun, 26 Jan 1992 15:46:06 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Sun, 26 Jan 1992 15:46:06 EST
Received:  from mit-eddie by kewgate.kew.com (UUPC/extended 1.11r) with UUCP;
           Sun, 26 Jan 1992 14:13:57 EST
Received: from OMNIGATE.CLARKSON.EDU by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA09935; Sun, 26 Jan 92 13:42:32 -0500
Received: from sun.soe.clarkson.edu by omnigate.clarkson.edu id aa02742;
          26 Jan 92 9:45 EST
Received: by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA10566; Sun, 26 Jan 92 09:04:01 EST
Return-Path: <@EDDIE.MIT.EDU:ffactory!ffactory.kew.com![e-mail]>
Received: from EDDIE.MIT.EDU by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA10562; Sun, 26 Jan 92 09:03:57 EST
Received:  by EDDIE.MIT.EDU with UUCP (5.65/25-eef)
    id AA04942; Sun, 26 Jan 92 09:02:12 -0500
Received:  from ffactory by kewgate.kew.com (UUPC/extended 1.11r) with UUCP;
           Sun, 26 Jan 1992 08:29:24 EST
Received:  by ffactory.kew.com (UUPC/extended 1.11s);
           Sun, 26 Jan 1992 07:52:51 EST
Date:      Sun, 26 Jan 1992 07:52:48 EST
From: "Snuffles P. Bear" <mit-eddie!kew.com!snuffles>
Message-Id: <[e-mail]>
Organization: Kendra Electronic Wonderworks
To: mit-eddie!plethora.media.mit.edu![e-mail]
Cc: UUPC Mailing List <[e-mail]>
Subject:   Re: option fixedspeed ?

On Sat, 25 Jan 1992 23:33:21 est, (Kent H Lundberg) mit-eddie!dobbs!klund wrote:
> Could you possibly give me a quick rundown of what option=fixedspeed
> does?  Exactly what do you mean by "autobaud the modem"?  I have a
> number of links around here that use V.42bis compression (with the
> serial ports operating at 4 times the connection speed) and it sounds
> like this is an option that I should be concerned about (or at least
> I should understand it) since it sounds like it applies to me...

The option is documented in the MAIL.PRN file.

Some modems, specifically the Hayes SmartModem series, will accept
commands at a certain port speed xxxx (say 2400 bps), and then if the
other modem it connects to is running a lower speed, issue a CONNECT
yyyy message at the original speed xxxx and *then* change its own port
speed to yyyy.  Thus, to continue talking to the modem, the computer
must switch to speed yyyy as well.

Autobauding is simply the process of the modems finding each other's
speed.  In some cases it also refers to the computer figuring out the
modem switched speed on it as well.

options=nofixedspeed

The default, options=nofixedspeed, tells the UUPC/extended to scan for a
number after the CONNECT and/or ANSWER strings defined in the *.MDM
file, and automatically switch the port speed to the that number if it
is found.

options=fixedspeed

options=fixedspeed, commonly used with Telebit Trailblzers, v.42bis
modems, and other data compressing modems, tells UUPC/extended to ignore
the connection speed and continue talking to the modem at the original
speed.  This is possible (and desired) because these modems buffer
characters to compress them, and thus can talk to the computer faster
than it sends the data down the telephone line.  (This is desired
because compress/decompression will result in more bits per second
exchanged with the computer than actually sent over the phone line.)

In summary, use nofixedspeed for most Hayes compatible modems, but
use fixedspeed for v.42bis, Telebits, or other data compressing modems.
Check your modem manual to determine whether it changes speed when it
connects.

Snuffles
--
Your faithful furry servant,    Chocolate: PO Box 132
Snuffles P. Bear                           Arlington, MA 02174-0002
                                Internet:  [e-mail]

 I just program for Drew because Binkley Bunny (who is as snowy white as
 I am) and Gunther Bear used to help Drew program from the top of
 kendra's monitor.  They went west in September [1990] with Mom so that
 Mom and Binkley could work on their PhDs.  That made the Wonderworks
 understaffed, so at Christmas [1990] Mom asked me to live with Drew.





















From mit-eddie!INDYVAX.IUPUI.EDU!ICBJ100 Sun, 26 Jan 1992 15:45:46 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Sun, 26 Jan 1992 15:45:46 EST
Received:  from mit-eddie by kewgate.kew.com (UUPC/extended 1.11r) with UUCP;
           Sun, 26 Jan 1992 12:19:00 EST
Received: from indyvax.iupui.edu by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA07852; Sun, 26 Jan 92 11:47:32 -0500
Received: from INDYVAX.IUPUI.EDU by INDYVAX.IUPUI.EDU (PMDF #12264) id
 <[e-mail]>; Sun, 26 Jan 1992 11:47 -0500
Date: Sun, 26 Jan 1992 11:46 -0500
From: "Michael R. Morrett" <mit-eddie!INDYVAX.IUPUI.EDU!ICBJ100>
Subject: FROGSHID.INF
To: [e-mail]
Message-Id: <[e-mail]>
X-Vms-To: IN%"[e-mail]"
X-Vms-Cc: ICBJ100

Hi Drew,

I have rewritted the documentaion for my UNIX host setup I sent you
and the person in Finland.

You have not told me to not send updates to you...
(For some reason, the above sentence looks weird, ie: stupid!)

For security reasons, I am using the hostname of 'frogshid' instead
of my real host name I have at work.  I work for the telephone
company and they would cut off my ..... if I gave any information a
hacker might use.

My PC is not called 'flybait', just made it up to be funny.  Also, I
have been trying for about three months to get a mail feed here in
Indianapolis.  I called in a favor to get a free mail account on the
local university and the temporary mail account expires May 1992. :-(

I'm still trying very hard to get a mail account and then I will
have a real UUCP node!  I LOVE "Star Trek" and have a nodename I think
is not used by anybody and that is also why I have not told anybody what
it is.

thanks,
mike
-------------------------------------------------------------------------------



     FROGSHID.INF         Sunday, January 26, 1992 10:30 am         Page 1


                                                        Michael R. Morrett
                                                 [e-mail]
                                                 Indianapolis, Indiana USA
                                                            1-317-265-1870

     Here is how my UNIX host is configured to run UUCP...

     +------------------+
     | Intergraph       |     +-------+                     +-------+
     | InterPro 2020    |     | Hayes |                     | Hayes |
     | UNIX Workstation X-----X V9600 | . . . . . . . . . . | V9600 |
     | System V 3.1     |  ^  | Modem |          ^          | Modem |
     | HoneyDanBer UUCP |  ^  +-------+          ^          +---X---+
     +------------------+  ^                     ^              |
          "frogshid"       ^              telephone line        |
                           ^                                    |
     25 pin male/female straight                        +-------X-------+
     through RS-232 cable (The                          | PC running    |
     workstation only has pins                          | UUPC/extended |
     1-8 & 20 cabled to the                             +---------------+
     modem port /dev/tty00.)                                "flybait"

     The Hayes modem is connected to port /dev/tty00 (the only port with
     modem control on the workstation).  This port is configured at 9600
     baud and with RTS/CTS hardware flow control.

     +-------------------+
     | /etc/inittab file |
     +-------------------+
     t0:234:respawn:/usr/lib/uucp/uugetty -r -t 30 tty00 9600H

     This port (tty00) is using uugetty to allow the port to dial in or
     dial out.  The "-r" flag causes uugetty to wait to read a character
     before it displays the login message.  The "-t" flag specifies the
     length of time in seconds (30 seconds for my host) uugetty will wait
     before aborting if no response.  The 9600H is a pointer to an entry
     in the /etc/gettydefs file.

     +---------------------+
     | /etc/gettydefs file |
     +---------------------+
     9600H# B9600 BRKINT IGNPAR ICRNL IXON IXANY OPOST ONLCR CS8 \
     CREAD ISIG HUPCL ECHO ECHOE ECHOK ICANON # B9600 BRKINT IGNPAR \
     ICRNL IXON IXANY OPOST ONLCR CS8 CREAD ISIG HUPCL ECHO ECHOE \
     ECHOK ICANON #login: #2400H

     2400H# B2400 BRKINT IGNPAR ICRNL IXON IXANY OPOST ONLCR CS8 \
     CREAD ISIG HUPCL ECHO ECHOE ECHOK ICANON # B2400 BRKINT IGNPAR \
     ICRNL IXON IXANY OPOST ONLCR CS8 CREAD ISIG HUPCL ECHO ECHOE \
     ECHOK ICANON #login: #1200H

     1200H# B1200 BRKINT IGNPAR ICRNL IXON IXANY OPOST ONLCR CS8 \
     CREAD ISIG HUPCL ECHO ECHOE ECHOK ICANON # B1200 BRKINT IGNPAR \
     ICRNL IXON IXANY OPOST ONLCR CS8 CREAD ISIG HUPCL ECHO ECHOE \
     ECHOK ICANON #login: #9600H



     FROGSHID.INF         Sunday, January 26, 1992 10:30 am         Page 2


     The "\" continuation character is NOT part of the lines above.  They
     are just three really long lines.  It is shown this way to make it
     "pretty" for this document.  The first line starts with 9600H# and
     ends with #2400H.  The second line starts with 2400H# and ends with
     #1200H.  The third line starts with 1200H# and ends with #9600H.

     The first part and last part of each line are labels.  The line in
     the /etc/inittab file says to read the line labeled 9600H in the
     /etc/gettydefs file.  If there is an error reading this line or the
     remote host or the remote user sends a BREAK, the label at the end of
     the 9600H line says to read the line labeled 2400H.  These labels
     provide a "goto" function.

     To create the three lines for modem use, a line in the existing
     /etc/gettydefs file labeled 9600 was copied to create three new lines
     labeled 9600H, 2400H, and 1200H.  CLOCAL was changed to HUPCL in two
     places in each line so that when the connection stops (carrier detect
     is lost), uugetty will die and drop the DTR lead.  The baud Bxxx
     settings in two places in each line also need to be changed.

     Besides HUPCL, another important option is CS8.  This sets the
     character size to eight (needed for "g" UUCP protocol).  The "man
     pages" for gettydefs(4) and termio(7) describe in detail the other
     options in the /etc/gettydefs file.

     +------------------+
     | /etc/passwd file |
     +------------------+
     uucp:*:5:1:admin & cron login:/usr/lib/uucp:
     nuucp:*:6:1:wkg login:/usr/spool/uucppublic:/usr/lib/uucp/uucico
     uubugs:xxx:6:1:wkg login:/usr/spool/uucppublic:/usr/lib/uucp/uucico
             ^
             |
     (13 character encrypted password)

     The "uucp" login is the administrative login id that "owns" all UUCP
     files and directories.  It is also used by cron to execute the UUCP
     maintenance programs.

     The "nuucp" login is the login id remote uucico programs will use to
     log into the local host.  For security reasons, this account on my
     host is disabled.  The "nuucp" account was copied to create a
     separate login for each remote host that calls my host.  For example,
     the "uubugs" login id will be used by the PC host "flybait".














     FROGSHID.INF         Sunday, January 26, 1992 10:30 am         Page 3


     +----------------------------+
     | /usr/lib/uucp/Systems file |
     +----------------------------+
     flybait Any ACU 9600 9=123-4567 "" \r\d\r in:--in: tadpole word: toad

     1       2   3   4    5          6  7      8        9       10    11
                                     \----------- chat script -----------/

     1 = remote host name
     2 = time to call
     3 = device type, an index pointing to the /usr/lib/uucp/Devices file
         (1st field).  ACU = Automatic Call Unit, a modem.
     4 = baud rate, an index pointing to the /usr/lib/uucp/Devices file
         (4th field)
     5 = remote host phone number
     6 = expect ""
     7 = send carriage return + delay (1-2 seconds) + carriage return
     8 = expect-send and subexpect-subsend information
         Expect "in:" (part of "login:").  If not received, send a
         carriage return or linefeed, look again for "in:".  Between the
         "--" is where the carriage return or linefeed is sent.  If
         needed, additional characters can be included between the "--".
     9 = send remote host login id
     10 = expect "word:" (part of "Password:")
     11 = send remote host password

     +----------------------------+
     | /usr/lib/uucp/Devices file |
     +----------------------------+
     ACU tty00 - 9600 hayes

     1   2     3 4    5

     1 = device type, pointed to by the /usr/lib/uucp/Systems file
     2 = physical device port
     3 = not used
     4 = baud rate, pointed to by the /usr/lib/uucp/Systems file
     5 = modem name, an index pointing to the /usr/lib/uucp/Dialers file
         (1st field)

     +----------------------------+
     | /usr/lib/uucp/Dialers file |
     +----------------------------+
     hayes =,-, "" \dAT "" \dAT OK-\dAT-OK \dATDT\T CONNECT

     1     2    3  4    5  6    7          8        9

     1 = modem name, pointed to by the /usr/lib/uucp/Devices file
     2 = "=" equals "," and "-" equals ","
         This allows the use of "=" and "-" in the /usr/lib/uucp/Systems
         file (fifth field) for the remote host phone number.  This
         translates the "=" and the "-" characters to the Hayes modem ","
         pause character.
     3 = expect ""
     4 = send delay + AT



     FROGSHID.INF         Sunday, January 26, 1992 10:30 am         Page 4


     5 = expect ""
     6 = send delay + AT
     7 = expect OK, if not received, send delay + AT again, expect OK
     8 = send delay + ATDT + remote host phone number.  The "\T" means use
         the information in the /usr/lib/uucp/Dialcodes file if needed.
     9 = expect CONNECT

     +------------------------------+
     | /usr/lib/uucp/Dialcodes file |
     +------------------------------+
     (I do not use.)

     +--------------------------------+
     | /usr/lib/uucp/Permissions file |
     +--------------------------------+
     LOGNAME=uubugs VALIDATE=flybait MACHINE=flybait \
             REQUEST=yes SENDFILES=yes \
             PUBDIR=/usr/spool/uucppublic/flybait \
             READ=/ WRITE=/usr/spool/uucppublic/flybait \
             COMMANDS=rmail

                         LOGNAME                  MACHINE
     Options             (remote calls local)     (local calls remote)
     ------------------  -----------------------  --------------------
     VALIDATE            Remote host must log in  Does not apply
                         with user id specified
                         by LOGNAME.  This links
                         MACHINE and COMMANDS
                         with a LOGNAME entry.

     REQUEST=yes/no      Can remote host request  Same meaning
                         files from local host
                         (default is no).

     SENDFILES=yes/call  Can local host send      Does not apply
                         files queued for remote
                         host (default is call,
                         only send when local
                         host calls remote host).

     READ=pathnames      Directories uucico may   Same meaning
                         read from (default
                         /usr/spool/uucppublic).

     WRITE=pathnames     Directories uucico may   Same meaning
                         write to (default
                         /usr/spool/uucppublic).

     COMMANDS=commands   Does not apply           Commands uuxqt will
                                                  execute for remote
                                                  host (default rmail).







     FROGSHID.INF         Sunday, January 26, 1992 10:30 am         Page 5


     +-------------------------+
     | /usr/lib/uucp/Poll file |
     +-------------------------+
     flybait<tab>9 13

     My host has a cron job execute the /usr/lib/uucp/uudemon.poll
     shell script at eight minutes before every hour.  This shell script
     checks the /usr/lib/uucp/Poll file to find remote hosts that are to
     be polled.  A work file named /usr/spool/uucp/flybait/C.flybaitn0000
     is then created. Another cron job executes the
     /usr/lib/uucp/uudemon.hour shell script (it runs uusched and uuxqt in
     the background) at four minutes before every hour.  As a result of
     these two cron jobs, the remote host "flybait" will be called at
     9:56am and 1:56pm.

     The work file name (C.flybaitn0000 for example) is created by UUCP in
     an unique way by adding "C." + first seven characters of remote host
     name + an ASCII character representing the grade (priority) of the
     work + a 4-digit job sequence number.  The "C" stands for Command
     file.  Uucico processes the file priority ("n" in this case) in order
     from A to Z and then a to z.  The latest sequence number is stored in
     the /usr/lib/uucp/SEQF file, but polling work files are always
     sequence number 0000.

     +--------------------------+
     | Hayes Modem Setup String |
     +--------------------------+
     AT&FM0Q2&C2&D3S0=1&Y0&W0&W1

     The modem is setup by executing the above command on a PC temporarily
     connected to the Hayes modem.  I have mixed luck trying to echo the
     modem setup string to the modem port (echo "AT&F..." > /dev/tty00).

     AT&F   recall factory configuration
     M0     turn speaker off
     Q2     return result codes in originate mode, do not return result
            codes in answer mode
     &C2    Pin 8 - presume presence of carrier detect (CD) signal until
            on-line, then monitor status of signal
     &D3    Pin 20 - monitor DTR signal and when an on-to-off transition
            of DTR signal occurs, hang up and perform a hard reset
     S0=1   answer on 1 ring
     &Y0    specify stored user profile 0 as power-up configuration
     &W0    write storable parameters as profile 0
     &W1    write storable parameters as profile 1

     Option Q2 (it appears most people use Q1) is used because it allows
     the modem result codes (OK, CONNECT, etc) to be seen on a manually
     dialed connection and disables the modem result codes in answer mode.
     If the modem echoes the result code (CONNECT for example) on an
     incoming call, the local uugetty will see the capital letters in the
     result code and think the remote host only understands uppercase.  At
     least three weeks of time was spent in tracking down this problem!





     FROGSHID.INF         Sunday, January 26, 1992 10:30 am         Page 6


     Option &C2 (it appears most people use &C1) is used because it allows
     a manually dialed connection to the modem (Kermit for example) even
     if carried detect is not present or enabled.  Because the
     /etc/gettydefs file has HUPCL, uugetty will NOT communicate with the
     modem without seeing carrier detect if option &C1 is used.

     Option &D3 (it appears most people use &D2) is used because this
     causes the modem to do a HARD reset when the line disconnects and DTR
     is dropped by uugetty.  A Zillion dollar phone bill would be a BIG
     shock!

     The &Y0, &W0, and &W1 commands make sure when the modem resets, it
     comes up in a known configuration.  My modem had a weird setup stored
     in profile 1 (from some other project) and &Y1 was set.  Again, it
     took a long time to figure out this problem.

     By default, the Hayes modem has RTS/CTS local hardware flow control
     (&K3) and V.42 error-control with V.42bis data compression (&Q5)
     enabled.

     +---------------+
     | Required Book |
     +---------------+
     "Managing UUCP and Usenet" by O'Reilly & Associates. (A new "10th
      Edition Revised and Update" book is now available.)

     +----------------+
     | Optional Books |
     +----------------+
     "UNIX Administration Guide for System V" by Rebecca Thomas & Rik
      Farrow. (This book has a very good 106 page chapter on UUCP.)

     "Using UUCP and Usenet" by O'Reilly & Associates

     "The Waite Group's UNIX Communications" by SAMS

     +---------+
     | Remarks |
     +---------+
     The hardest part about UUCP is the modem setup string, then the chat
     script.

     The first modem on my workstation was a NEC modem that has about
     3,000,000 setup commands and the factory default configuration makes
     absolutely no sense.  At first, I thought my problems were with the
     chat script until I discovered the NEC modem has a factory default
     setting of NO flow control!  About TWO months of time was spent
     trying to get UUCP to work with the NEC modem!!  After the NEC modem
     was replaced with a Hayes modem, UUCP started working just great! :-)

     If you have any comments (good or bad), corrections, questions,
     PLEASE send me mail!























From mit-eddie!sun.soe.clarkson.edu!uupc-info-request Tue, 28 Jan 1992 17:08:15 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Tue, 28 Jan 1992 17:08:15 EST
Received:  from mit-eddie by kewgate.kew.com (UUPC/extended 1.11s) with UUCP;
           Tue, 28 Jan 1992 16:09:59 EST
Received: from OMNIGATE.CLARKSON.EDU by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA01990; Tue, 28 Jan 92 15:40:16 -0500
Received: from sun.soe.clarkson.edu by omnigate.clarkson.edu id aa11985;
          28 Jan 92 0:01 EST
Received: by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA12505; Mon, 27 Jan 92 23:01:13 EST
Return-Path: <omega!ash>
Received: from eros.uknet.ac.uk by sun.soe.clarkson.edu (4.1/SMI-4.1)
    id AA12500; Mon, 27 Jan 92 23:00:57 EST
Received: from cctal.uucp by eros.uknet.ac.uk with UUCP
          id <[e-mail]>; Tue, 28 Jan 1992 00:36:48 +0000
Received: from omega by cctal.UUCP (UUPC/extended 1.11n) with UUCP;
          Mon, 27 Jan 1992 23:00:32 gmt
Received: by omega.UUCP (UUPC/extended 1.11q); Mon, 27 Jan 1992 22:46:45 GMT
Date: Mon, 27 Jan 1992 22:46:43 GMT
From: Andrew Hardie <mit-eddie!omnigate.clarkson.edu!omega!ash>
Message-Id: <[e-mail]>
To: UUPC Mailing List <[e-mail]>
Subject: Mail forwarding to PRN


Someone posted recently about wanting to be able to forward files to
a printer. He wanted to use uucp. I don't use uucp, but I am doing it
with mail. Here's how:

(1) Get yourself the DOS ports of some essential Unix tools for doing this
    sort of messing around: cat, sed, grep and, while you are at it, mv.
    Should be listed along with the Nutshell books as required UUPC items.

(2) set up a password file entry like:
    prinput:*:::printer input:/usr/prinput

(3) in /usr/prinput, make a FORWARD file with:
    | cat > prn

Mail to prinput goes straight to the printer. That's it.

OK, you are left with the headers, but I am sure a whizz with sed (i.e. not
me) can knock up a little script to chop the headers off (delete everything
from the Ctrl-As or the From up to the first blank line?), so that the
FORWARD becomes:

| sed -f chophead.sed > prn

or some such.

I am sure there are many other ways of cracking this nut, this is just
an example.

Andrew
--
+----------------------------------------------------------------------------+
| Andrew Hardie                                               [e-mail] |
| London, England                                      uknet!cctal!omega!ash |
+----------------------------------------------------------------------------+





















From ffactory.kew.com!help Fri, 31 Jan 1992 20:01:18 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Fri, 31 Jan 1992 20:01:18 EST
Received:  from ffactory by kewgate.kew.com (UUPC/extended 1.11s) with UUCP;
           Fri, 31 Jan 1992 19:42:15 EST
Received:  by ffactory.kew.com (UUPC/extended 1.11s);
           Fri, 31 Jan 1992 19:06:09 EST
Date:      Fri, 31 Jan 1992 19:06:04 EST
From:      "Drew Derbyshire - UUPC/Extended Help" <[e-mail]>
Message-ID: <[e-mail]>
Organization: Kendra Electronic Wonderworks
To:        [e-mail]
Cc:        "UUPC Mailing List" <[e-mail]>,
           [e-mail]

Delete the commands=all.  ALL *must* be upper case if used, but you
should NEVER NEVER NEVER authorize a strange system to ALL commands.
The PSI folks are wonderful people, but I don't even grant ALL commands
to people within the kew.com domain I've personally known 12 years.

-ahd-
--
Drew Derbyshire         UUPC/extended e-mail:  [e-mail]
                    Chocolate Ice Cream Fund:  Post Office Box 132
                                               Arlington, MA 02174-0002 USA

"Hi Snuffles!!"                                 - The Grey-eyed Elf





















From ffactory.kew.com!help Sat, 01 Feb 1992 07:58:24 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Sat, 01 Feb 1992 07:58:24 EST
Received:  from ffactory by kewgate.kew.com (UUPC/extended 1.11s) with UUCP;
           Sat, 01 Feb 1992 07:25:03 EST
Received:  by ffactory.kew.com (UUPC/extended 1.11s);
           Sat, 01 Feb 1992 07:03:41 EST
Date:      Sat, 01 Feb 1992 07:03:37 EST
From:      "Drew Derbyshire - UUPC/Extended Help" <[e-mail]>
Message-ID: <[e-mail]>
Organization: Kendra Electronic Wonderworks
To:        (Dwatney Farthinghale III) mit-eddie!bikini.cis.ufl.edu!arms!0
Cc:        "UUPC Mailing List" <[e-mail]>,
           [e-mail]
Subject:   Re: making a list server

On Tue, 28 Jan 1992 09:34:04 EST, (Dwatney Farthinghale III) mit-eddie!bikini.cis.ufl.edu!arms!0 wrote:
> Hi,
>      I'm trying to set up a small list server through my system.  I have
> aliases set up so that local mail can be sent to multiple people, but I dont
> know how to set things up so that mail from a remote system can be done the
> same way.  for example, if i have the alias "test_list" defined to send mail
> to 10 different local or remote users, what do i have to do so that a remote
> user could send mail to "[e-mail]" and having it do the same
> thing?

Aliases are only used by the user interface, which as you have
discovered, doesn't enter into the picture for remote mail.

Add the mailing list address to the PASSWD file, and put all the
addresses in a FORWARD file for the mailingf list address, and then then
mail to that addresses.  Be forewarned that that mail will bounce to the
original person who sends the mail, since such a simple list doesn't
handle actually re-queueing the mail from the list.

-ahd-
--
Drew Derbyshire         UUPC/extended e-mail:  [e-mail]
                    Chocolate Ice Cream Fund:  Post Office Box 132
                                               Arlington, MA 02174-0002 USA

"Hi Snuffles!!"                                 - The Grey-eyed Elf





















From mit-eddie!dobbs!dobbs.cambridge.ma.us!klund Sat, 22 Feb 1992 07:03:00 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Sat, 22 Feb 1992 07:03:00 EST
Received:  from mit-eddie by kewgate.kew.com (UUPC/extended 1.11s) with UUCP;
           Sat, 22 Feb 1992 01:30:37 EST
Received: from plethora.media.mit.edu by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA27797; Thu, 20 Feb 92 11:45:01 -0500
Received: by plethora.media.mit.edu (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0-plethora)
    id AA12731; Thu, 20 Feb 92 11:43:09 EST
Received:  by dobbs.cambridge.ma.us (UUPC/extended 1.11q);
           Thu, 20 Feb 1992 11:20:31 est
Date:      Thu, 20 Feb 1992 11:20:29 est
From: "Kent H Lundberg" <mit-eddie!dobbs.cambridge.ma.us!klund>
Message-Id: <[e-mail]>
Reply-To: "Kent H Lundberg" <mit-eddie!dobbs.cambridge.ma.us!klund>
To: [e-mail]

Drew,
    May I suggest that you include this file in the next
release of the UUPC11_D.ZIP file?  It describes the US Domain.
Currently, people may register hosts in the US domain, (which
has its own name servers) for no charge.
    (As you'll probably notice, I just registered my host,
dobbs.cambridge.ma.us.  It was much easier that I expected.  The
hardest part was convincing my mailserver that it was a good
idea, but now it works great!)
    Just trying to be helpful,
        Kent.

PS : UUnet now charges $50 for domain registration... you
may want to update uunetdom.inf.


                The US Domain
                =============

Introduction:

The US domain is an official top-level domain in the Domain Name
System (DNS) of the Internet community.  It is registered with the
Network Information Center (DDN-NIC).  The domain administrators are
Jon Postel and Ann Westine Cooper at the Information Sciences
Institute of the University of Southern California (USC-ISI).

The US domain hierarchy is based on political geography, that is, the US
domain is subdivided into states, then cities, and so on.  Any computer
in the United States may be registered in the US domain.

Typical host names in the US domain are:

        VIXIE.SF.CA.US
        DOGWOOD.ATL.GA.US
        KILLER.DALLAS.TX.US
        HOLODEK.SANTA-CRUZ.CA.US
        GRIAN.CPS.ALTADENA.CA.US

Membership:

Because many computers in the United States are already registered in
the COM, EDU, and other top level domains, relatively few computers are
currently registered in the US domain.  However the US Domain is
beginning to grow.

In the past the computers registered the US Domain were primarily
owned by small companies or individuals (and often located in homes).
It is expected than many more computers of all types and belonging to
all sizes of organizations will be registered in the US Domain.

Large organizations or companies are also encouraged to register in
the US Domain.  Typically these have many hosts and will operate their
own DNS name servers.  The US Domain will delegate an appropriate part
of the name space to such large organizations on the same terms as the
NIC requires for delegations of portions of the COM or EDU domains.

Administration:

Currently, the US Domain and all of its subdivisions (i.e., states,
cities etc.) are managed by the US Domain Registrar.  The US Domain is
just beginning to grow and we want to be careful about what names get
used and how control is allocated until some usage patterns are
established.  We will run the servers for all the states in the US
domain.

Registration of a host in the US domain does not grant permission to use
the Internet or its component networks.  Any restrictions on sending
mail through (or other use of) the Internet is independent of host
registration in the US domain.  Registration in the US domain does not
allocate any IP address, or cause registration in HOSTS.TXT.

There is no change in the procedures for registration in, or operation
of, other top-level domains such as COM, EDU, GOV, MIL, NET, or ORG.
These domains are not being moved under the US domain.

Delegation:

At some future point we will hand off the administration of individual
states to appropriate responsible people, probably in the state they
administer.  Early experience shows that delegation of cities and of
companies within cities is most practical.  The delegated part of the
name space will most likely be in the form of
<org-name>.<city>.<state>.US.

           For example:  IBM.ARMONK.NY.US.

Generally, organizations requesting delegations must provide at least
two independent DNS name servers in physically separate locations on
the Internet that provide the the domain service for translating names
to addresses in this domain.

The state codes are those assigned by the US Postal Service.  Cities
may be named (designated) by their full name (spelled out with hyphens
replacing spaces (e.g., Los-Angeles or New-York)), or by a city code.
The first choice is the full city name, the second choice is the city
codes from Western Union's "City Mnemonics" list, and a third choice
is a code for your city that you choose.  However, it is very
desirable that all users in the same city use the same designator for
the city.

         For example:  Joes-Bar.Santa-Monica.CA.US

Groups:

The administrator of a company or the organizer of a group (or "domain
park") of users with individual hosts may coordinate the registration of
the group by forwarding all the information for the group to the US
Domain Administrator.

In this case, the explicit specific information for each host must be
provided.  All fully qualified names must be unique.  If a host is not
directly on the Internet an MX record is required pointing to an
Internet host for forwarding.  The forwarding host must be directly on
the Internet (that is, have an IP address), no "double MX-ing" is
allowed.

A group coordinator of, for example, the Computer Club in Chicago (CLUB),
could arrange to coordinate the registration of all the computers used
by members of the club.  The registered names might have the form:

    ALPHA.CLUB.CHI.IL.US   MX   10   CS.CHICAGO-U.EDU

Only hosts on the Internet can act as forwarding hosts.  Hosts on
networks such as CSNET, UUCP, BITNET, must be registered with an
Internet forwarding host.  When registering a destination host in the US
domain with an MX record, the requester is responsible for also
registering the destination host with the administrator of the
forwarding host.

For example, when a message is sent to "[e-mail]"
it will be routed to the Internet host "CS.CHICAGO-U.EDU" as directed
by the MX record.  The host "CS.CHICAGO-U.EDU" must know some way of
delivering the message to the host "ALPHA.CLUB.CHI.IL.US" (uucp, slip,
whatever).  So the destination host (ALPHA.CLUB.CHI.IL.US) must be
known to (registered with) the forwarding host (CS.CHICAGO-U.EDU), as
well as being registered in the US domain DNS database.

The administrator of the destination host must make an agreement with
the administrator of the forwarding host for the forwarding service.
This agreement must be in place before the request for registration is
sent to the US Domain Administrator.

Other Networks:

A section of the DNS database is called a "zone".  With careful
coordination, a domain (like EDU) can be divided into several zones.
This has been done for the EDU and COM domains to aid in the
registration of hosts from the UUCP, CSNET and BITNET communities.  If
a host is registered in UUCP, BITNET, or CSNET portion of a domain (as
something.EDU or something.COM), it need not be registered in the US
domain, unless a geographical name (something.city.state.US) is
desired.

If a host is in a UUCP, BITNET, or CSNET network, it doesn't need to
register in the US domain, unless it wants to be registered with a
geographical DNS domain name.

Only hosts on the Internet can act as forwarding hosts.  Hosts on
networks such as CSNET, UUCP, BITNET, etc., must affiliate their hosts
with an Internet host.  This is necessary because when messages for
your host arrive at the Internet host it will need to know where to
forward them.  MX records are necessary.

Unique Name:

It is the policy that a computer must have a single primary name, so it
should not be registered in both US and COM (or both US and EDU).  It is
possible to have "nicknames" for a brief period while a host name change
is in progress.

Wild Cards:

While we strongly believe that it is in everyone's interest and good
for the Internet to have each host explicitly registered (that is, we
believe that wild cards should not be used), we also realize that not
everyone agrees with this belief.  Thus, we will allow wild card
records in the US domain under groups or organizations.  For example,
"*.BIRDSONG.SUVL.CA.US".

Servers:

The US domain is currently supported by four name servers:

VENERA.ISI.EDU, VAXA.ISI.EDU, HERCULES.CSL.SRI.COM, and NNSC.NSF.NET.

Cost:

Currently, there is no cost for registering a host in the US domain.

References:

RFC-974,  Partridge, C., "Mail Routing and the Domain Name System".
RFC-1034, Mockapetris, P., "Domain Names - Concepts and Facilities".
RFC-1035, Mockapetris, P., "Domain Names - Implementation and Specification".

Registration:

To register in the US Domain send a message to the US Domain Registrar
([e-mail]).  The response will be a US Domain Questionnaire for
you to fill out.

In several cities a "coordinator" has volunteered to process requests
locally and communicate with the US Domain Registrar on behalf of all
interested users in that city, or organization within that city.  If
in your request we see that you are in a city or organization with a
coordinator we will refer you to that coordinator.

More Information:

For more information about the US domain please contact:
    Ann Westine Cooper at ([e-mail]).


--
Kent H Lundberg                   [e-mail]
                      3 Ames Street #242, Cambridge, MA 02139
also : [e-mail]            voice/fax [phone]





















From ffactory.kew.com!help Sat, 22 Feb 1992 11:57:04 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Sat, 22 Feb 1992 11:57:04 EST
Received:  from ffactory by kewgate.kew.com (UUPC/extended 1.11s) with UUCP;
           Sat, 22 Feb 1992 10:13:48 EST
Received:  by ffactory.kew.com (UUPC/extended 1.11s);
           Sat, 22 Feb 1992 09:15:32 EST
Date:      Sat, 22 Feb 1992 09:14:51 EST
From:      "Drew Derbyshire - UUPC/Extended Help" <[e-mail]>
Message-ID: <[e-mail]>
Organization: Kendra Electronic Wonderworks (Arlington, MA)
To:        mit-eddie!uunet.uu.net!uworld!alans
Subject:   Re: Need Info

On Wed, 12 Feb 92 09:33:10 -0500, mit-eddie!uunet.uu.net!uworld!alans wrote:
> We are mentioning your WonderWorks product in a review and would
> like information on pricing, as well as location of compnay,
> contact names, etc. Also, if you want, please send a press
> kit to:
>         Alan Southerton
>         Product Reviews Editor
>         UNIXWORLD Magazine
>         234 Cabot Street #9
>         Beverly, MA 01915

Alan,

You can publish any of the following as you chose.  Lucky for us, you
won't have room for it all.

When are you going to do this review?  We are constantly putting out new
releases, and we're late enough in the cycle that I can get you the next
release (1.11s or 1.11t) the day after it is released.  The soonest we
could get out a release is in about two weeks (3/8/92).

The current official release is 1.11q.  If you should have happen to
find 1.11r (a beta release), don't test it, go back to 1.11q.

---> Part I

Contact Address:

U.S. Snail:     Andrew H. Derbyshire
                Kendra Electronic Wonderworks
                P. O. Box 132
                Arlington, MA 02174

Internet:       [e-mail]

UUCP:           uunet!mit-eddie!kendra!help

Telephone:      [phone]

We *strongly* prefer to receive e-mail over both snail mail and phone
calls.

Distribution:

UUPC/extended is distributed electronically; the primary method is
anonyous FTP over the Internet.  It can also be retrieved from at least
two BBS systems without charge (except for long distance charges), or
ordered on diskette from a company in Potsdam, NY.  The full
HOWTOGET.TXT file which included with each release follows; you can
extract what you wish from it, and include a note to send e-mail to
[e-mail] for the full retrieval instructions.

The source is included with the program.

Basic softcopy documentation is included with UUPC/extended.  No
hardcopy documenation is included, although this can be requested when
registering.

Pricing:

UUPC/extended is, at its most basic level, free.

Most new users of UUCP oriented mail systems should buy the Nutshell
Handbooks "Using UUCP and USENET" and "Managing UUCP and USENET" from
O'Reilly & Associates.  People should consider the costs of these books
when totalling the cost of setting up a UUPC/extended system.  (The
Wonderworks is not associated with O'Reilly & Associates; we just read
their stuff.)

Beginning the fall of 1991, people can register UUPC/extended to support
the expenses of producing it, including our hardware and
telecommunications costs.  They can also optionally support the staff's
love of Chocolate Ice Cream.  The information to register is included in
the documentation archive as well.

Registering is not required to use the programs; we would rather see
people using an unregistered copies than paying money for a worse
program.  (In other words, Snuffles would rather be famous than rich.)

Support:

Support is normally done via e-mail to [e-mail] or the Internet
mailing list for UUPC/extended. Registered users can also get phone
support.  Bug fixes are shipped as a part of new releases; we never
slip-stream fixes or apply changes to back-level code.

As previously noted, source is always available.  The program requires
MicroSoft C 6.0 or Borland C++ 2.0 to compile, plus a Macro Assembler
(MASM or TASM).

---> Part II

Now comes the funny parts; hence the switch from editorial we to first
personal singular.  Save this, it's your press kit.

UUPC/extended is a very real program, make no mistake; the source code
requires 1.6 Megabytes, over half of which was written by me personally.
I am told by others it is among the best of the UUCP programs for DOS
available, including comments from various people that UUNET recommends
it for people hooking up DOS machines to UUNET.  (I'd confirm this
latter fact before publishing it.)

But, as for the Wonderworks itself, it's a little more complicated than
that.  For starters, my chief assistant's full name is Snuffles Polar
Bear; she's a 12 inch tall plush Gund who lives on kendra's monitor.
(Ooops.  Make that 12 inch tall _cute_ plush Gund; Recycled Paper
Products even has a card with her picture on it.)  She sends e-mail (her
address is [e-mail]), write documentation, and sometimes even
does bug fixes.

In other words, we're all a little weird over here in Arlington.

A little history ... enter ramble mode.

UUPC was originally written for a number of platforms in the mid-1980's
by a crew up in Vancouver, B.C., and posted to the Net with a GNU-ish
Copyleft in the source files.  While still at Clarkson University in
1986, I encountered an early version but was unable to get it to work
because of incompatible hardware.

In 1989, I tried the second widely distributed of version of UUPC,
(commonly known as UUPC 1.05 or just the interim release).  It worked,
but had problems.  In getting it to behave for my use on a system I
registered as kendra, I created UUPC/extended 1.06a.  I made additional
changes until I worked up my way up to 1.07c by the end of that year.

In 1989, I also met an MIT co-ed, Katherine E. Williams, over the net; I
then moved to Boston for unrelated professional reasons.  When I chose
to seek an internet domain for my system in early 1990, Katherine let me
back into her initials as a joke, and thus was created Kendra Electronic
Wonderworks (kew.com).  (Another choice was Kickbacks, Wirefraud, and
Extortion, which doesn't look good in a family magazine like UNIX World.
I try to plan ahead.)

About the time I registered kew.com with the Internet NIC, I also
started giving away UUPC/extended to the unsuspecting.  My original
policy was staying not-for-profit by neither accepting money nor
spending money on UUPC; the former worked, the latter didn't.  Thus,
I have given up on the latter but still distribute the source and
accept pleas from help from the unregistered.

I am the primary author, but not the sole author.  As a partial list:
The UUCP command was written in England, a prototype of the OS/2 support
was done in Germany, news and RN support (which is still in testing) was
written in Los Angles and updated in San Francisco, UUX/UUXQT
enhancements were written in Texas, and improved serial port support was
written here in the Bay State.  Also, bug fixes come from everywhere.

As for Snuffles the Plush Programming Polar Bear, Katherine gave
Snuffles to me for Christmas 1990 to replace two other creatures she
left in my care the previous summer.  Those creatures currently live on
the monitor of Katherine's system, athena.kew.com, in Santa Barbara.
Creatures, computer, and fiance are moving back here next month.

Snuffles used to ask for Chocolate in all her e-mail, then someone sent
her 144 (18 pounds!) of Snickers Bars.  Now, she's only allowed to ask
for donations to the Chocolate Ice Cream fund.  (There's this ice cream
place in the MIT student union ...)

End of history ... exit ramble mode.

For additional UUPC/extended background and credits, be sure to read the
README.PRN file included with the documentation archive.

-ahd-
--
Drew Derbyshire         UUPC/extended e-mail:  [e-mail]
                    Chocolate Ice Cream Fund:  Post Office Box 132
                                               Arlington, MA 02174-0002 USA

 UUPC/extended is "system crash" spelled sideways.





















From mit-eddie!adm.brl.mil!info-ibmpc-request Sat, 28 Mar 1992 13:39:30 EST remote from kendra
Received:  from kendra by ffactory.kew.com (UUPC/extended 1.11s) with UUCP;
           Sat, 28 Mar 1992 13:39:30 EST
Received:  from mit-eddie by kew.com (UUPC/extended 1.11s) with UUCP;
           Sat, 28 Mar 1992 12:19:12 EST
Received: from ADM.BRL.MIL by EDDIE.MIT.EDU with SMTP (5.65/25-eef)
    id AA18093; Sat, 28 Mar 92 11:24:09 -0500
Date: Sat, 28 Mar 92 11:24:09 -0500
From: mit-eddie!adm.brl.mil!info-ibmpc-request
Received: by ADM.BRL.MIL id aa19118; 28 Mar 92 6:44 EST
Received: from ADM.BRL.MIL by ADM.brl.MIL id ab17897; 28 Mar 92 5:42 EST
Received: from adm.brl.mil by ADM.BRL.MIL id aa17744; 28 Mar 92 5:16 EST
Message-Id:  <[e-mail]>
Apparently-To: <premise![e-mail]>
Apparently-To: <[e-mail]>

=RETURN-PATH:[e-mail]
_brl.mil
brl.mil
Message-ID: <[e-mail]>
Date: Tue, 24 Mar 92 22:24:47   GMT
From: "Info-IBMPC Digest" <[e-mail]>
Reply-To: [e-mail]
Subject: Info-IBMPC Digest V92 #52
To: "Info-IBMPC Distribution": ;

Info-IBMPC Digest           Tue, 24 Mar 92       Volume 92 : Issue  52

Today's Editor:
         Gregory Hicks - Rota Spain <[e-mail]>

Today's Topics:
      Recent msdos uploads to SIMTEL20 (Feb 16 - Mar 15 1992)

Send Replies or notes for publication to: <[e-mail]>

Send requests of an administrative nature (addition to, deletion from
the distribution list, et al) to: <[e-mail]>

Addition and Deletion requests for UK readers should be sent to:
<[e-mail]>

Archives of past issues of the Info-IBMPC Digest are available by FTP
ONLY from WSMR-SIMTEL20.ARMY.MIL in directory PD2:<ARCHIVES.IBMPC>.

----------------------------------------------------------------------

Date: Sun, 15 Mar 1992  13:22 MST
From: Keith Petersen <[e-mail]>
Subject: Recent msdos uploads to SIMTEL20 (Feb 16 - Mar 15 1992)

The following files have been recently uploaded to SIMTEL20
(between 16-Feb-92 and 15-Mar-92):

NOTE: Type B is Binary; Type A is ASCII

 Filename   Type Length   Date    Description
==============================================
Directory PD1:<MSDOS.4DOS>
PKBTM111.ZIP  B   10759  920312  4DOS batch file serves as archiver shell

Directory PD1:<MSDOS.ARC-LBR>
AC212.ZIP     B   47120  920312  Converts between any two archive types
AM71.ZIP      B  210807  920312  ArcMaster front-end/convert for .ARC/.ZIP/.LZH
HPACK75.ZIP   B   66431  920312  High performance archiver from New Zealand

Directory PD1:<MSDOS.AT>
ATCLOK.ZIP    B    5989  920312  Use hardwre clock instead of DOS for time/date

Directory PD1:<MSDOS.AUTOCAD>
ELEBLKS.ZIP   B   50134  920312  Electrical symbols for AutoCAD

Directory PD1:<MSDOS.BATUTL>
EVERY15.ZIP   B   11223  920312  BATutil: Execute cmd if given time has passed
FDATE61A.ZIP  B   40668  920312  Date manipulation utility for batch files
TSBAT33.ZIP   B   78856  920312  Collection of useful batch files by Timo Salmi

Directory PD1:<MSDOS.BBS>
ACF540R0.ZIP  B  362135  920312  QBBS/RA/SBBS total file system w/CD-ROM supprt
FDSEC200.ZIP  B   43926  920312  Security package for BBS Front Door v2.00

PD1:<MSDOS.BBSDOORS>
PHONE266.ZIP  B   59248  920312  Split screen BBS Chat door. Fossil required

Directory PD1:<MSDOS.BBSLISTS>
313BBS25.ZIP  B   18834  920312  Horst Mann's 313 area BBS list. Feb. 17, 1992

Directory PD1:<MSDOS.C>
HANDLES.ZIP   B   20112  920312  Get >20 handles in TC (also DJGPP). Docs & src

Directory PD1:<MSDOS.CAD>
PSPIC43A.ZIP  B  298990  920312  Pspice 4.3, Electrical Circuit Simulator, 1/4
PSPIC43B.ZIP  B  304468  920312  Pspice 4.3, Electrical Circuit Simulator, 2/4
PSPIC43C.ZIP  B  329313  920312  Pspice 4.3, Electrical Circuit Simulator, 3/4
PSPIC43D.ZIP  B  320778  920312  Pspice 4.3, Electrical Circuit Simulator, 4/4

Directory PD1:<MSDOS.CALCULATOR>
EVAL104.ZIP   B   30442  920312  EVAL v1.04: Mathematical expression evaluator
PIBCAL11.ZIP  B   35739  920312  Programmable calculator, with Turbo Pascal src

Directory PD1:<MSDOS.CPLUSPLUS>
DPMIFI.ZIP    B    9652  920312  Borland C++v3.00 DPMILOAD DV-compatibility fix

Directory PD1:<MSDOS.CROSSASM>
AS11V103.ZIP  B   34135  920312  Assembler for Motorola 68HC11 MicroController

Directory PD1:<MSDOS.DATABASE>
FISHBYTE.ZIP  B  217487  920312  Fishbyte: Salt water fishing and Loran log pgm
JOGGR105.ZIP  B   59053  920312  Runner's log and analysis database, v1.05
MM-631.ZIP    B  139255  920312  MealMaster database program for recipes, v6.31

Directory PD1:<MSDOS.DBASE>
POPDBF40.ZIP  B  149617  920312  TSR: Popup view, edit, print, read dBASE files
WAMPUM42.ZIP  B  362496  920312  dBASE III-compatible datadase management syst.

Directory PD1:<MSDOS.DESKACCESS>
JOTIT2.ZIP    B   33642  920312  JotIt: Netbios-compatible phone message taker
PHONEM50.ZIP  B   36437  920312  Fast phone number indexer (not a TSR)
XASC10.ZIP    B   34048  920312  Pop-up extended (256 character) ASCII table

Directory PD1:<MSDOS.DESKPUB>
BUSPM.ZIP     B   35431  920312  Business icons for Printmaster
PEANUTS2.ZIP  B    8690  920312  Peanuts Gang icons for Printmaster
PMMED.ZIP     B   11189  920312  Medical icons for Printmaster

Directory PD1:<MSDOS.DESQVIEW>
DSHELL.ZIP    B  263525  920312  Unix-like COMMAND.COM replacement for DESQview
DVC18.ZIP     B   58212  920312  DV Commander: Command-line control of DESQview
DVFAQ2.ZIP    B   19558  920312  Questions and answers on DESQview, QEMM
DVSI2_00.ZIP  B  233443  920312  15 DV utils: performance,printing,window mgmt
RBMGR101.ZIP  B    1896  920312  Reboot Manager: Carrier detect monitor for DV

Directory PD1:<MSDOS.DIRUTL>
DELDIR10.ZIP  B   14356  920312  Safe recursive directory and file removal pgm
DFS097.ZIP    B   16158  920312  Delete/find/calc. size of files/directory tree
MOVE453.ZIP   B   13345  920312  Move files from one drive/directory to another
RCD151.ZIP    B   25933  920312  Ray's Change Directory - fast and intuitive
WIZ251.ZIP    B   33832  920312  Fast file find utility with many filters

Directory PD1:<MSDOS.DISASM>
BUBBLE.ZIP    B   85743  920312  Bubble: A disassembler for COM or EXE programs
DIS86122.ZIP  B   75632  920312  Disassembler for 8086, 80286, 80386 programs

Directory PD1:<MSDOS.DSKUTL>
ACT204.ZIP    B  175630  920312  ActaeOn v2.04: Graphical hard disk manager
ATFMT100.ZIP  B   36552  920312  Floppy formatter. Gets 1066K on 720K diskette
DRS120.ZIP    B  116131  920312  Data Recovery Software: Reads BAD disks
KLSPACE.ZIP   B   11239  920312  Keith Ledbetter's graphical disk space display
MICROPLS.ZIP  B   42444  920312  List of parameters for Micropolis drives
PRUNE21.ZIP   B   10026  920312  Clear out unallocated bytes at the end of file
TDCHK110.ZIP  B   14301  920312  TeleDisk image file validator. SYDEX

Directory PD1:<MSDOS.EDITOR>
ADAMI90.ZIP   B  153222  920312  Tamil word processer in 16 colors
TERSE12.ZIP   B   20735  920312  Full-screen Ed. Brief-like commands. Only 4K

Directory PD1:<MSDOS.EDUCATION>
ABCTLK23.ZIP  B  207303  920312  Teaches children to talk, read/alphabet/spell
CAPFUN.ZIP    B   31360  920314  DEMO: prog. teaches sentence capitalization
FRNCH102.ZIP  B   90714  920312  Ultimate French v1.02: Learn basic French
LIE33.ZIP     B   85934  920312  Analysis of differential equations
LP100210.ZIP  B  210606  920312  Linear programming, solve optimizing problems
LTBLIT30.ZIP  B  119613  920312  Potato late blight management game for Windows
SFS101.ZIP    B  277775  920312  Space Flight Simulator, CGA/HGC/EGA/VGA
SM2.ZIP       B   91354  920312  Learning tool; automated repetitave study
SPNSH102.ZIP  B   95757  920312  Ultimate Spanish v1.02:  Learn basic Spanish
USGEO102.ZIP  B  130285  920312  USA geography teacher & tester (req. EGA/VGA)

Directory PD1:<MSDOS.EMULATORS>
JPP-B1.ZIP    B   36513  920312  Sinclair ZX Spectrum 48K emulator, req 386+VGA
MCX11V15.ZIP  B   73874  920312  MC68HC11 MicroController multitask eXecutive
SIM68102.ZIP  B   80820  920312  Motorola 68HC11 MicroController simulater

Directory PD1:<MSDOS.FILEDOCS>
AAAREAD.ME    A    4423  920312  Information about the files in this directory
DOWNLOAD.INF  A    1810  920314  How to get SIMTEL20 files via telephone modem
SIMIBM.ARC    B  366854  920315  Comma-delim list of all MSDOS files w/descrip.
SIMLIST.ARC   B  326938  920315  Text format list of all MSDOS files w/descrip.
UPLOAD.INF    A    1482  920314  How to upload programs to SIMTEL20

Directory PD1:<MSDOS.FILUTL>
UUEXE510.ZIP  B   31751  920312  R.E.Marks' UUdecode/UUencode/XXdecode/XXencode
ZCOPY101.ZIP  B   14297  920312  SHARE-aware copying utility by Peter Stewart

Directory PD1:<MSDOS.FINANCE>
DEBTFREE.ZIP  B  147103  920312  Home mortgage mgr, calculate/record payments
ECON.ZIP      B   68682  920312  ECON: Econometric stock market forcasting

Directory PD1:<MSDOS.FLOWCHART>
TMASTR23.ZIP  B  262811  920312  Task Master v2.3: All purpose project tracking

Directory PD1:<MSDOS.FORTH>
FORTHCOM.ZIP  B  100907  920312  Native Code Forth Compiler:COM,EXE,SYS,TSR,ROM
FPC355-1.ZIP  B  335473  920312  Forth-PC compiler, w/editor & examples, 1of5
FPC355-2.ZIP  B  321760  920312  Forth-PC compiler, w/editor & examples, 2of5
FPC355-3.ZIP  B  341823  920312  Forth-PC compiler, w/editor & examples, 3of5
FPC355-4.ZIP  B  340569  920312  Forth-PC compiler, w/editor & examples, 4of5
FPC355-5.ZIP  B  303155  920312  Forth-PC compiler, w/editor & examples, 5of5

Directory PD1:<MSDOS.FORTRAN>
FTNCHK25.ZIP  B   67800  920314  FTNCHEK: Fortran code analyzer for debugging
TOKEN.FOR     B    2226  920312  Tokenize a string (C 'StrTok') for Fortran 77

Directory PD1:<MSDOS.GIF>
NAKED101.ZIP  B  320320  920314  NakedEye v1.01, a SuperVGA GIF viewer
VUIMG330.ZIP  B  123136  920312  GIF/GIF89a/PCX/TIFF view/print, zoom/pan/scale

Directory PD1:<MSDOS.GNUISH>
00MSDOS.GNU   A   26743  920312  Explains the MSDOS GNU-ish project
00README.GCC  A   25098  920312  Explains how to find the GNU gcc port to msdos
INDE11AS.ZIP  B   66083  920312  GNU Indent: 'C' pgm reformatter (C src only)
INDE11AX.ZIP  B   37994  920312  GNU Indent: 'C' pgm reformatter (EXE & doc)

Directory PD1:<MSDOS.GRAPHICS>
ALCH151.ZIP   B  384567  920312  Targa/EPS/GIF/IFF/JPEG/PCX/Sun/TIFF/BMP convrt
EEDPR23S.ZIP  B   63368  920312  C sources for EEDRAW23.ZIP drivers. TC/BC++
EEDRW23S.ZIP  B  121824  920312  C sources for EEDRAW23.ZIP program. TC/BC++
FRAIN172.ZIP  B  448901  920312  FRACTINT v17.2 EGA/VGA/XGA fractal generator
FRASR172.ZIP  B  777944  920312  C & ASM src for FRACTINT v17.2 fractal gen.
GLE33A.TXT    A    3677  920312  Installation instructions for GLE graphics pkg
GLE33A_1.ZIP  B  359424  920312  GLE Scientific Graphs, Slides, (Core & Screen)
GLE33A_2.ZIP  B  397824  920312  GLE PostScript Driver & Expanded Memory versns
GLE33A_3.ZIP  B  629248  920312  GLE Epson & Laserjet device drvrs &extra fonts
GLE33A_4.ZIP  B  465920  920312  GLE Utilities, surface plotting, HPGL driver
ITERANT.ZIP   B   40350  920312  Makes bifurcation graphical plots, w/QB4.5 src
SPLT240.ZIP   B  152654  920312  Advanced HP-GL & DXY-GL pen plotter simulator

Directory PD1:<MSDOS.INFO>
ALTMPX33.ZIP  B    3842  920312  Alternate multiplex interrupt proposal v3.3
COMP0292.ZIP  B   20662  920312  DRC's directory of computer companies 02/92
CON0292.ZIP   B   40489  920312  DRC's directory of corporate controllers 02/92
DOSREF22.ZIP  B  241113  920312  List of interrupts, memory locations, IO ports
DVFAQ2.ZIP    B   19558  920312  Questions and answers on DESQview, QEMM
FAX0292.ZIP   B   48596  920312  DRC's directory of corporate FAX numbers 02/92
FTPLIST.ZIP   B   39480  920312  List of Internet sites with FTP & mail access
HR0292.ZIP    B   63577  920312  DRC's directory of human resources execs 02/92
MIS0292.ZIP   B   35773  920312  DRC's directory of MIS executives 02/92
MKT0292.ZIP   B   50642  920312  DRC's directory of sales/mktg executives 02/92
MODER.LST     B    9221  920312  List of MS-DOS FTP sites and their moderators
TL0292.ZIP    B    9408  920312  DRC's directory of telecomm companies 02/92
TRE0292.ZIP   B   35384  920312  DRC's directory of corporate treasurers 02/92
TSFAQ26.ZIP   B  101251  920312  T.Salmi: Frequently asked questions & answers
XGAQOS.ZIP    B    1935  920312  QOS tech bulletin on IBM XGA standard

Directory PD1:<MSDOS.IRIT>
INTRLIB1.ZIP  B  104670  920312  IRIT Interaction library 1.0. BC++, DJGPP
IRIT386E.ZIP  B  523191  920312  IRIT 3.0 EXEs for 386/486 using DJGPP 1.05
IRITSM3E.ZIP  B  559207  920312  IRIT 3.0 executables using BC++ 3.0
IRITSM3S.ZIP  B  697255  920312  IRIT 3.0 solid modeler src for BC++/DJGPP/Unix

Directory PD1:<MSDOS.KA9Q-TCPIP>
VIEW9201.ZIP  B  381868  920312  Electronic mail program for use w/KA9Q TCP/IP

Directory PD1:<MSDOS.KEYBOARD>
CMDEDT21.ZIP  B   79999  920312  cmdline ed w/history/completion/aliases/SOURCE
PB19C.ZIP     B   30738  920312  TSR runs keystrokes from self-made .COM file
REGAIN.ZIP    B   44451  920312  Cmd-line editor, history recall, aliases, etc.

Directory PD1:<MSDOS.LAN>
LANMENU2.ZIP  B   69948  920312  Lanmenu 2.0: Local Area Network DOS shell menu
MAILCALL.ZIP  B   25653  920312  LAN: TSR util provides pop-up access to ccMail
MSG_14.ZIP    B    3049  920312  Novell Msg interceptor w/alarm, popup window
NFSML202.ZIP  B   21376  920312  NFS Mail: Unix mail reader for use with PC-NFS
SFC33.ZIP     B   66750  920312  Serial File Copy v3.3: PC to PC file transfers

Directory PD1:<MSDOS.MENU>
FASTM60A.ZIP  B  237453  920312  FastMenu 6.0, graphical menu system, 1 of 2
FASTM60B.ZIP  B  274568  920312  FastMenu 6.0, graphical menu system, 2 of 2
PM600-1.ZIP   B  350588  920312  Brown Bag's Power Menu program, v6.00. 1 of 2
PM600-2.ZIP   B  313793  920312  Brown Bag's Power Menu program, v6.00. 2 of 2

Directory PD1:<MSDOS.MODEM>
EZ136.ZIP     B  185565  920312  EZ-Reader for Qmail, v1.36 (PC Board/ProDoor)
HSLK11B1.ZIP  B   89695  920312  HS/Link external protocol driver, Beta v1.1
JMOD311.ZIP   B  104159  920312  Jmodem file transfer protocol, with C source
OFFLI136.ZIP  B  125945  920312  Offline: QWK mail manager by Harvey Parisien
XPC.FRM       A    5635  920312  Order form for getting X.PC files on disk
XPC401.ZIP    B  475316  920312  X.PC v4.00+ communications driver, with source

Directory PD1:<MSDOS.NETWORK>
PCBRI121.ZIP  B   75908  920312  Use PC as a cheap Ethernet-Ethernet Bridge
PCRTE223.ZIP  B  234485  920312  Make PC into TCP/IP router for about $450

Directory PD1:<MSDOS.OPUS>
OMAN_174.ZIP  B  254796  920312  BBS manager for OPUS version 1.7x

Directory PD1:<MSDOS.PASCAL>
PNL010.ZIP    B  123504  920312  The Pascal NewsLetter, issue #10, March 1992

Directory PD1:<MSDOS.PCMAG>
VOL11N05.ZIP  B   43134  920312  PcMag: DD.SC, OPENSPEC.XLA, REBOOT.BAS, WINPTR
VOL11N06.ZIP  B   49419  920312  PcMag: CLRPRI, MIDIDE, PCDICT, PCUNZP, TRYALT

Directory PD1:<MSDOS.PCTECHNIQUES>
PCTV1N1.ZIP   B   85355  920312  PC Techniques mag listings - April/May 1990
PCTV1N2.ZIP   B   31116  920312  PC Techniques mag listings - June/July 1990
PCTV1N3.ZIP   B   29416  920312  PC Techniques mag listings - Aug/Sept. 1990
PCTV1N4.ZIP   B   29620  920312  PC Techniques mag listings - Oct./Nov. 1990
PCTV1N6.ZIP   B   41548  920312  PC Techniques mag listings - Feb/March 1991
PCTV2N1.ZIP   B   36844  920312  PC Techniques mag listings - April/May 1991
PCTV2N4.ZIP   B   25458  920312  PC Techniques mag listings - Oct./Nov. 1991
PCTV2N6.ZIP   B   36794  920312  PC Techniques mag listings - Feb/March 1992

Directory PD1:<MSDOS.PKTDRVR>
3C503.ZIP     B   13690  920312  3c503 pkt drvr; works w/shared memory disabled
DRIVERS3.ZIP  B   61432  920314  Updates to 10.x packet driver release

Directory PD1:<MSDOS.QBASIC>
IQB9202.ZIP   B    7253  920312  Inside QuickBasic source listing, Feb. 1992
IQB9203.ZIP   B   10068  920312  Inside QuickBasic source listing, March 1992

Directory PD1:<MSDOS.RAMDISK>
SRDISK13.ZIP  B   49600  920312  Resizeable XMS ramdisk capable of >32M disks

Directory PD1:<MSDOS.SCREEN>
NNANS192.ZIP  B   67648  920312  Enhanced/fast ANSI.SYS replacement, COM or SYS
SPS21.ZIP     B   37228  920312  Make PrtSc print parts of screen, many options
VIZ423.ZIP    B   78522  920312  VIz v4.23 BIOS & DOS video acceleration util.

Directory PD1:<MSDOS.SNOBOL4>
VSNBL220.ZIP  B  250971  920312  Vanilla SNOBOL4, PD vers. 2.20 of the language

Directory PD1:<MSDOS.SOUND>
PCTALK21.ZIP  B  139748  920312  Digitized speech/music on PC speaker. DEMO
SCOPTRAX.ZIP  B  246814  920312  Super PC sound/sample editor with a scope
SOUND.ZIP     B   21174  920312  Plays .VOC & .SND files thru PC speaker

Directory PD1:<MSDOS.STARTER>
00-FILES.DOC  A    7857  920314  All about file types in the SIMTEL20 archives
SIMTEL20.INF  A   16272  920312  Complete overview of the SIMTEL20 archives

Directory PD1:<MSDOS.STATISTICS>
NONLIN10.ZIP  B  159508  920312  Nonlinear regression analysis

Directory PD1:<MSDOS.SYSUTL>
BREAK.ZIP     B    3593  920312  Inhibit CTRL-C in DOS but not in program
CONFISET.ZIP  B    9321  920312  Export DR-DOS config environ to 4DOS (w/src)
COUNT.ZIP     B    6032  920312  Execute a specified command after X reboots
CRON28.ZIP    B   49880  920312  Timed command dispatcher; like Unix cron
PCC.DOC       A    1491  920312  PC-Choices installation (for PCC.ZIP)
PCC.ZIP       B  753552  920312  PC-Choices object-oriented 386 operating syst.
RESET.ZIP     B    2176  920312  Presses the reset button or CTRL+ALT+DEL
SHROM19C.ZIP  B   19148  920314  ShellRoom v1.9c: Swap program from MEM to disk
TSRCOM34.ZIP  B   75275  920312  TSR memory managmt utils (MARK/RELEASE/MAPMEM)
TSRSRC34.ZIP  B   75334  920312  Source code for TSRCOM v3.4 pkg. (TASM, TP6.0)
TSUTLE16.ZIP  B   53693  920312  Fifth set of command-like utilities, T.Salmi

Directory PD1:<MSDOS.TELIX>
SALTB.ZIP     B   22518  920312  Telix SALT-language source code beautifier

Directory PD1:<MSDOS.TROJAN-PRO>
AAVIRUS.ZIP   B   14955  920312  Check/save/restore disk boot record/MBR
CHK4FE.ZIP    B   33822  920312  Front-end driver for CHK4COMP.ZIP, needs mouse
CPAVSE.ZIP    B  225888  920312  Central Point Anti-Virus special free edition
HCOPY14.ZIP   B   66759  920312  COPY with virus protection, from Hilgraeve
I-M111A.ZIP   B  280814  920312  Integrity Master data integrity/anti-virus sys
NAVM.ZIP      B  199856  920312  Norton's AntiVirus, free Michelangelo edition
STEALTH.ZIP   B   56220  920312  Self-scanning executable w/TP and MSC source
TBSCAN33.ZIP  B   86502  920312  Thunderbyte Virus Scan 3.3; needs VSIGyyxx.ZIP
TBSCNX30.ZIP  B   69933  920312  Thunderbyte XScan v3.0 TSR; needs VSIGyyxx.ZIP
VIRSH11E.ZIP  B   80364  920312  ViruShell: Shell for McAfee's anti-viral pgms
VIRX21.ZIP    B   79510  920312  VIRx, v2.1: Easy to use free virus scanner
VSIG9201.ZIP  B   18020  920312  Virus signatures for HTSCAN/TBSCAN - v92#01

Directory PD1:<MSDOS.TURBO-C>
EXPR11.ZIP    B   15464  920314  Expression parsing, differentiating lib for TC

Directory PD1:<MSDOS.TURBOPAS>
CLEARMEM.ZIP  B    1713  920312  TP unit to init stack, heap & global variables
INASM10.ZIP   B   24060  920312   Inline assembler generator for TP, w/src
JPDOOR32.ZIP  B  177802  920312  TP 5.5 & 6.0 BBS door writing TPU utilites
OMOUSE.ZIP    B   22476  920312  Object-oriented mouse for Turbo Pascal 5.5
PDIR10.ZIP    B   12581  920312  Palcic's directory routines using TP 5.5 OOP
TP55TSR.ZIP   B   33217  920312  TSR unit for Turbo Pascal 5.5 applications
TPFLEX.ZIP    B   25807  920312  Turbo Pascal 5.5 linked lists, generic
TPMUL221.ZIP  B    7226  920312  Make your TP 6.0 programs DV/Win/TV/DDOS aware
TPREAL1.ZIP   B   10323  920313  Improved 'real' routines for Turbo Pascal
TPV24.ZIP     B    4738  920312  Fast interrupt-driven serial comm rtns for TP

Directory PD1:<MSDOS.TXTUTL>
FLEX237.ZIP   B  286819  920312  Fast Unix-like LEX lexical analyzer for MS-DOS
INDXX802.ZIP  B  244272  920312  Make back-of-book index from page proofs. DEMO
KWS111.ZIP    B   16845  920312  Keyword Search: And/or finds in text files
SSPELL12.ZIP  B   99384  920312  TurboC++ or Unix C source for Unix Spell clone
TXS25.ZIP     B   56330  920312  Fast text search with existential dictionaries

Directory PD1:<MSDOS.UUCP>
UUCPFAQ.ZIP   B   11574  920312  uucp frequently asked questions by Ian Taylor

Directory PD1:<MSDOS.WAFFLE>
APPSIG.ZIP    B   13803  920312  Roy's Signature Picker for Waffle BBS
ATMOVE.ZIP    B    7892  920312  Move Waffle BBS files and @files description
BAT164A.ZIP   B   13985  920312  Tom Dell's batcher for Waffle - can feedbymail
DISKHOG.ZIP   B   14418  920312  List the top 10 Waffle BBS users by disk usage
FSEDWAFL.ZIP  B    2560  920312  Examples of how to use fsed with your Waffle
GENPASS.ZIP   B    6568  920312  Generate passwords for Waffle BBS
GRAFFITI.ZIP  B   46075  920312  Allows Waffle BBS users to generate graffiti
HK-SET.ZIP    B   24441  920312  Hunt & Kill message file delete for Waffle BBS
LINES.ZIP     B   10575  920312  Add Lines: headers to Waffle BBS postings
NEWUSER.ZIP   B   12757  920312  Push files into Waffle BBS user directories
PMAIL02.ZIP   B    3946  920312  Waffle BBS Perl Mail reader by Budi Rahardjo
PRIVLIST.ZIP  B   10520  920312  List Waffle BBS users with certain priv level
PURGEDIR.ZIP  B    9214  920312  Delete old user directories on Waffle BBS
QUOTA01.ZIP   B   19409  920312  Jonathan Herr's Disk quota program for Waffle
REQ.ZIP       B   10067  920312  Display requests file entry for a Waffle user
RETRY10.ZIP   B   17194  920312  Poll pgm for Waffle, more flexible than PPOLL
TRIM.ZIP      B    6980  920312  Trim whitespace from ends of lines
VOTE.ZIP      B   17419  920312  A voting booth for Waffle BBS
WAFDAY.ZIP    B   21074  920312  Display Waffle BBS daily usage statistics
WAFDB.ZIP     B    9410  920312  Convert the waffle 1.64 password file to ASCII
WAFDL111.ZIP  B   21344  920312  External file section door for Waffle's BBS
WAFM10.ZIP    B   66733  920312  WafMail 1.0: Offline mail door for Waffle BBS
WAFPROT.ZIP   B    1421  920312  Waffle BBS external protocols - sample setups
WUTL10.ZIP    B   39485  920312  A collection of Waffle BBS (mail) utilities

Directory PD1:<MSDOS.WINDOWS3>
BENVELOP.ZIP  B   78381  920312  WIN3: Addresses envelope incl. postal barcodes
FILEMA21.ZIP  B   49211  920312  Windows3 file manager copy/move/rename/delete
FRONTW11.ZIP  B  125242  920312  Enhanced file manager for Windows 3, ver 1.1
METER.ZIP     B   19931  920312  Windows Mag. disk space meter, (req. VBRUN100)
OOT-1-03.ZIP  B   83927  920312  WIN3: OO Documentation Tool; OoaToolFree v1.03
PFP219.ZIP    B  118714  920312  Programmer's text file printer for Windows 3
WCRON22G.ZIP  B  199691  920312  Unix's cron-like utility for Windows 3.0/3.1
ZM301.ZIP     B   88627  920312  ZIP/LHARC shell for Windows 3.0 w/mouse supp.
ZM30W.ZIP     B   82548  920312  WIN3: ZIP/LHARC shell (with BIOS bug fix)

Directory PD1:<MSDOS.ZIP>
PCUNZIP.ZIP   B   18718  920312  Fast free UNZIP program, with ASM source
ZLAB-19C.ZIP  B  274505  920312  Ziplab v1.9C; a ZIP file tester for PCBoard
ZM28.ZIP      B  142708  920312  ZipMaster 2.8, ZIP file compression manager

SIMTEL20 files are also available from mirror sites OAK.Oakland.Edu
(141.210.10.117), wuarchive.wustl.edu (128.252.135.4), ftp.uu.net
(137.39.1.9), nic.funet.fi (128.214.6.100), src.doc.ic.ac.uk
(146.169.3.7) or archie.au (139.130.4.6), by e-mail through the
BITNET/EARN file servers, or by uucp from UUNET's 1-900-GOT-SRCS.
See UUNET file uunet!~/info/archive-help for details.

If you cannot access them via FTP or e-mail, most SIMTEL20 MSDOS
files, including the PC-Blue collection, are also available for
downloading from Detroit Download Central [phone].  DDC
has multiple lines which support 300/1200/2400/9600/14400 bps
(103/212/V22bis/HST/V32bis/V42bis/MNP).  This is a subscription system
with an average hourly cost of 17 cents.  It is also accessable on
Telenet via PC Pursuit and on Tymnet via StarLink outdial.  New files
uploaded to SIMTEL20 are usually available on DDC within 24 hours.

Public, private or corporate institutions and libraries interested in
the SIMTEL20 MS-DOS collection in CD-ROM format bundled with library
card-catalog type access and duplication software can contact Coyote
Data, Ltd. by mail at 1142 N. Main, Rochester, MI 48307 or by FAX at
[phone].  Others who do not need the access and duplication
software should send e-mail to [e-mail] (Robert Bruce)
or telephone [phone] for details on his CD-ROM offer.

Keith Petersen
Maintainer of the MSDOS, MISC and CP/M archives at SIMTEL20 [192.88.110.20]
Co-SysOp, Detroit Download Central 313-885-3956 (V22bis/HST/V32bis/V42bis/MNP)
Internet: [e-mail]     or       [e-mail]
Uucp: uunet!umich!vela!w8sdz                          BITNET: w8sdz@OAKLAND

------------------------------

End of Info-IBMPC Digest V92 #52
********************************
-------





















From help Mon, 21 Sep 1992 17:37:18 EDT
Received:  by kendra.kew.com (UUPC/extended 1.11w);
           Mon, 21 Sep 1992 17:37:18 EDT
Date:      Mon, 21 Sep 1992 17:37:11 EDT
From:      "Drew Derbyshire - UUPC/Extended Help" <[e-mail]>
Message-ID: <[e-mail]>
Organization: Kendra Electronic Wonderworks (PO Box 132, Arlington, MA 02174)
To:        "Mark Purcell" <[e-mail]>
Cc:        [e-mail],
           "UUPC Mailing List" <[e-mail]>
Subject:   Re: Anonymous uucp login

On Mon, 21 Sep 1992 20:34:13 GMT, [e-mail] wrote:
> Hi Drew,
>
> I'm trying to get anonymous uucp login working but am having some problems.
> I'm running uupc 1.11v and this is what my uucico.log is spitting out:
>
> uucico.log
> -----------
> 09/21-18:55 UUCICO: UUPC/extended 1.11v (Sep 02 1992 23:02:55)
> 09/21-18:55 callin: Waiting for answer on port COM2 device HAYES24 for 184 minutes
> 09/21-18:56 login: login user nuucp (*anonymous) at Mon, 21 Sep 1992 18:56:26 GMT
> 09/21-18:56 pos called by fonsc: 1200 bps, g protocol, z grade
> 09/21-18:56 Receiving "D.fonsc0RXd" as "D.fonsc0RXr" (*anonymo/D/#ms~2k-x.r}i)
> 09/21-18:56 reof: Unable to rename TMP1.$$$ to *anonymo/D/#ms~2k-x.r}i
> 09/21-18:56 *anonymo/D/#ms~2k-x.r}i: No such file or directory
> 09/21-18:56 Extended DOS Error Information: Number = 3, Class = 8, Action = 3, Locus = 2
> 09/21-18:56 reof: Deleting corrupted file TMP1.$$$
> 09/21-18:56 process: Aborting connection to *anonymous, previous system state = q
> 09/21-18:56 0 files sent, 0 files received, 6 bytes sent, 58 bytes received
> 09/21-18:56 13 packets transferred, 0 errors, connection time 0:11, 5 bytes/second
> -----------
>
> As you can see the system then kicks out the anonymous host, I can't create the
> *anonymo directory so I don't know what to do.

You can't receive files into the anonymous directory.  That's a feature.
This prevents anonymous system from queuing a request such as a UUCP
back to it and having a second anonymous system pick up the first
system's request by mistake.

It also prevents an anonymous system from sending mail to you, which is
also by design.  This prevents a horde of security and response
problems.

Anonymous systems can write the public directory if you choose to let
them.

-ahd-
--
Drew Derbyshire         UUPC/extended e-mail:  [e-mail]

 I have not lost my mind; it's backed up on tape on somewhere.





















From cs.utexas.edu!cactus.org!hen3ry Mon, 12 Oct 1992 16:13:19 EDT remote from mit-eddie
Received:  from mit-eddie by kendra.kew.com (UUPC/extended 1.11w) with UUCP;
           Mon, 12 Oct 1992 16:13:19 EDT
Received: from cs.utexas.edu by eddie.mit.edu id aa13237; 12 Oct 92 15:36 EDT
Received: from cactus.org by cs.utexas.edu (5.64/1.142) with UUCP
    id AA23215; Mon, 12 Oct 92 14:45:14 -0500
Received: by cactus.org (4.1/SMI-4.1)
    id AA20354; Mon, 12 Oct 92 13:11:48 CDT
From: Henry Velick <[e-mail]>
Message-Id: <[e-mail]>
Subject: UUPC/extended & 4DOS
To: UUPC bugz & maintenance <[e-mail]>
Date: Mon, 12 Oct 92 13:11:48 CDT
X-Mailer: ELM [version 2.3 PL11]

Drew,

Just got the new UUPC/extended. Followed all the installation
instructions. Haven't yet set up a mail server, but thought I'd
test it locally. Everything I tried gave me something like:

  c:\util\comm\uucp } mail -s "Clang Honk Tweet" postmaster
  MAIL: UUPC/extended 1.11v (02Sep92 23:02)
  Changes Copyright (c) 1989 by Andrew H. Derbyshire.  Changes and
  Compilation Copyright (c) 1990-1992 by Kendra Electronic Wonderworks.  May
  be freely distributed if original documentation and source is included.

  Enter message.  Enter ~? for help.  End input with a period (.)
  ? This be a test.
  ? .

  Abort, Continue, Edit, List, or Send? Send
  rmail: No such file or directory
  Extended DOS Error Information: Number = 3, Class = 8, Action = 3, Locus = 4
  Unable to execute rmail; mail not delivered.

  c:\util\comm\uucp }

Everything, that is, until I tried ditching 4DOS and running mail
under COMMAND.COM. Then all went smoothly. The workaround is easy:
a batch file that sets up the path and environment variables and
invokes COMMAND /c mail %&. That last is 4DOS's way of including
the rest of the command line.

Works like a champ, so far, but I thought you'd like to know about
this incompatibilty. Anyone who uses COMMAND when 4DOS is available
(or CMD rather than 4OS2), really is missing a lot. Thanks for a
cool tool, and you'll probably hear more from me soon.

--
\-- Henry Velick   \  Millions long for immortality, who don't know what   \
 \-- Datalingus     \  to do with themselves on a rainy Sunday afternoon.   \
  \-- Austin, Texas  \ -----------------------------------      Susan Ertz   \
   \-- 512-459-5770   \ Purveyors of Fine Graphics Software and Consultation  \






















From mit-eddie!adm.brl.mil!info-ibmpc-request Wed, 02 Dec 1992 18:25:30 EST remote from pandora
Received:  from pandora by kendra.kew.com (UUPC/extended 1.11x) with UUCP;
           Wed, 02 Dec 1992 18:25:30 EST
Received:  from mit-eddie by kendra.kew.com (UUPC/extended 1.11x) with UUCP;
           Wed, 02 Dec 1992 00:16:04 EST
Received: from adm.brl.mil by eddie.mit.edu id ab29999; 1 Dec 92 23:25 EST
Received: from ADM.BRL.MIL by ADM.brl.MIL id ac07987; 1 Dec 92 15:38 EST
Received: from adm.brl.mil by ADM.BRL.MIL id aa07730; 1 Dec 92 15:02 EST
Message-ID: <[e-mail]>
Date: Sun, 29 Nov 92 00:27:33   GMT
From: Info-IBMPC Digest <[e-mail]>
Reply-To: [e-mail]
Subject: Info-IBMPC Digest V92 #183
To: Info-IBMPC Distribution: ;

Info-IBMPC Digest           Sun, 29 Nov 92       Volume 92 : Issue 183

Today's Editor:
         Gregory Hicks - Rota Spain <[e-mail]>

Today's Topics:
              FTP for Internet sites with E-Mail only

Send Replies or notes for publication to: <[e-mail]>

Send requests of an administrative nature (addition to, deletion from
the distribution list, et al) to: <[e-mail]>

Addition and Deletion requests for UK readers should be sent to:
<[e-mail]>

Archives of past issues of the Info-IBMPC Digest are available by FTP
ONLY from WSMR-SIMTEL20.ARMY.MIL in directory PD2:<ARCHIVES.IBMPC>.

----------------------------------------------------------------------

Date: Sat, 21 Nov 92 07:50:56 EST
From: Message Center <[e-mail]>
Subject: FTP for Internet sites with E-Mail only.

One of the features of the Internet is the ability to connect to
another location and obtain files stored at that location.  This
capability is called "FTP" (for "File Transfer Protocol".)  This
means that an installation can place important sources or binaries on
a particular machine and then "advertise" the place where the
material is stored.  Then, anyone who wants or needs this material
can use FTP to request it.  There are two types of FTP, one where you
have advance permission and have a specific account and password on
that system, and one where the system allows anyone to request files
from it.  The latter is done by using the "standard" account name of
"anonymous" with your internet address as your password, and is known
as "anonymous FTP".

Note:  If you are using a system on BITNET, you have special
capabilities through a different method.  See the bottom of this memo
for additional details.

FTP can be for small to enormous file areas.  Columbia University
provides an anonymous FTP site to allow people to obtain the sources
to the Kermit file transfer protocol.  In some cases, such as the
massive SIMTEL20 archive operated by the White Sands Missle Range,
this includes thousands of files which can be used by the IBM-PC,
Macintosh, Amiga and other systems.

While some people who either have university or commercial service
accounts have the ability to do FTP directly to their local machine,
then download the files from their local machine, a lot more people
have E-Mail only access to Internet, and thus have no means available
to do FTP and acquire these files.

However, there is a way to obtain files from FTP sites and retrieve
files by E-Mail.  This service is available by sending E-Mail
messages to the FTPMAIL service provided by Digital Equipment
Corporation to anyone with an Internet E-Mail address.  In fact, DEC
operates an anonymous FTP site called "gatekeeper" that if you don't
ask for a specific other site, it will make requests from gatekeeper.

To be able to do E-Mail based FTP, you need to know the name of the
site, then you simply tell FTPMAIL and ask it to obtain the files for
you if that site permits "anonymous" FTP, i.e. where anyone can
obtain any file from the system.  You send the message, and FTPMAIL
eventually will either (1) send you back confirmation or (2) send you
back a note saying you made a mistake.  If you got (1), it will then
send you the requested files, in chunks of 64K or less.  If the file
is smaller than 64K, you get it in one message.  If the file is
larger than 64K, you get it in multiple messages.  (If you are on
Compuserve, you need to set this limit to 49K; send a HELP message to
find out about the CHUNKSIZE command.)

I personally have used this method to send over 10 megabytes of files
to me at my account on MCI Mail.  Note that you must know the system
you want to retrieve and the exact file names.  In almost all
instances, the particular case, UPPER OR lower, is critical and must
be done exactly as indicated based on a listing from a DIR request.

The way to make E-Mail FTP requests is to send a message to:

        [e-mail]

where a set of commands are sent as the text of the message.  (The
title of the message is not used except to identify file(s) returned
to you.)

The full instructions can be obtained by sending a message with: HELP
as a line in the text of the message.  The complete FTPMAIL
capability includes other features including non-anonymous FTP,
ability to retrieve a file in different sized pieces, and special
password capability.

The general method of sending a request is as follows (lines
beginning with ; are comments; these comments are not included on
FTPMAIL requests):

TO:  [e-mail]
; FTPMAIL's address
CONNECT WSMR-SIMTEL20.ARMY.MIL
; This is the name of the system I want to request from
REPLY [e-mail]
; Here is where I want files I receive sent to
BINARY
UUENCODE
; These two lines indicate I will be receiving 8-bit character
; files and they should be sent to me as uuencoded binary so
; that they can be sent as E-Mail.  If you are only doing DIR
; requests, you can skip both of these
GET PD1:<MSDOS.DBASE>WAMPUM42.ZIP
; Here I am requesting the system send me a particular file
; I am interested in.  Note that you can only request 10 files
; at a time, more than that and your request is rejected
DIR PD1:<MSDOS>
; Here I want a directory listing.  This will come back as a
; separate message
QUIT
; This is an optional command indicating that there are no more
; FTPMAIL commands.  If your system appends tag lines or disclaimers,
; to your messages, you should put this in so FTPMAIL will ignore
; them.

NOTE:  If your local system is a BITNET system, however, you can use
the BITFTP server from Princeton, whose syntax is slightly different,
and allows special features including direct binary transfers as
opposed to DEC's FTPMAIL which, since it is running on the Internet
as opposed to internal BITNET transfers, cannot provide this
capability.  To use the BITNET server, you should send a message with
HELP as the text to "[e-mail]".  BITFTP will not send files
to non-BITNET sites.

Paul Robinson -- [e-mail]  -- These opinions are mine alone.

------------------------------

End of Info-IBMPC Digest V92 #183
*********************************
-------





















From /dev/null Fri, 18 Dec 1992 02:46:45 EST remote from kendra
Received:  from kendra by kendra.kew.com (UUPC/extended 1.11x) with UUCP;
           Fri, 18 Dec 1992 02:46:45 EST
Path: kendra!eddie.mit.edu!micro-heart-of-gold.mit.edu!news.bbn.com!usc!zaphod.mps.ohio-state.edu!uwm.edu!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!nigel.msen.com!emv
From: [e-mail] (Edward Vielmetti)
Newsgroups: comp.mail.uucp
Subject: Re: My new domain name -- what do I do with it?
Date: 17 Dec 1992 00:56:14 GMT
Organization: Msen, Inc. -- Ann Arbor, Michigan
Lines: 12
Message-ID: <[e-mail]>
References: <[e-mail]>
NNTP-Posting-Host: garnet.msen.com
X-Newsreader: TIN [version 1.1 PL8]

Michael Faurot ([e-mail]) wrote:
: :
: : 1) Send $50 to UUNET and have them set up name servers for you. E-mail
: :    [e-mail].

Msen will do the same for $35, and if you don't have a real machine to
deliver the mail to we'll drop it in any mailbox on the planet (internet,
MCI, Compuserve, what not).  E-mail [e-mail].

  Edward Vielmetti, vice president for research, Msen Inc. [e-mail]
        Msen Inc., 628 Brooks, Ann Arbor MI  48103 +1 313 998 GLOB